public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 255276ceded76952ecf13741a9b8063f3197cb0b
Date: Sat, 07 Jan 2012 21:04:49 +0100	[thread overview]
Message-ID: <20120107200452.81DDB200BA@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2888 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 3.x development tree".

The branch, master has been updated
       via  255276ceded76952ecf13741a9b8063f3197cb0b (commit)
       via  8d003a2e5e118fe67f2647dd7717b80c38f0cfc4 (commit)
      from  2c4fd909065842b4cce786116db2d585ed4d29fc (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 255276ceded76952ecf13741a9b8063f3197cb0b
Merge: 2c4fd90 8d003a2
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sat Jan 7 20:56:09 2012 +0100

    Merge remote-tracking branch 'stevee/perl-Crypt-PasswdMD5'

commit 8d003a2e5e118fe67f2647dd7717b80c38f0cfc4
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date:   Sat Jan 7 20:44:06 2012 +0100

    perl-Crypt-PasswdMD5: New package.

-----------------------------------------------------------------------

Summary of changes:
 .../perl-Crypt-PasswdMD5.nm                        |   29 +++++++------------
 1 files changed, 11 insertions(+), 18 deletions(-)
 copy perl-XML-Parser/perl-XML-Parser.nm => perl-Crypt-PasswdMD5/perl-Crypt-PasswdMD5.nm (56%)

Difference in files:
diff --git a/perl-Crypt-PasswdMD5/perl-Crypt-PasswdMD5.nm b/perl-Crypt-PasswdMD5/perl-Crypt-PasswdMD5.nm
new file mode 100644
index 0000000..8eb1500
--- /dev/null
+++ b/perl-Crypt-PasswdMD5/perl-Crypt-PasswdMD5.nm
@@ -0,0 +1,46 @@
+###############################################################################
+# IPFire.org    - An Open Source Firewall Solution                            #
+# Copyright (C) - IPFire Development Team <info(a)ipfire.org>                   #
+###############################################################################
+
+name       = perl-Crypt-PasswdMD5
+version    = 1.3
+release    = 1
+arch       = noarch
+thisapp    = Crypt-PasswdMD5-%{version}
+
+groups     = Development/Libraries
+url        = http://search.cpan.org/dist/Crypt-PasswdMD5
+license    = GPL+
+summary    = Provides interoperable MD5-based crypt() functions.
+
+description
+	This package provides MD5-based crypt() functions.
+end
+
+source_dl  = http://search.cpan.org/CPAN/authors/id/L/LU/LUISMUNOZ/
+
+build
+	requires
+		perl(ExtUtils::MakeMaker)
+	end
+
+	build
+		perl Makefile.PL INSTALLDIRS=vendor
+		make %{PARALLELISMFLAGS}
+	end
+
+	make_install_targets = pure_install PERL_INSTALL_ROOT=%{BUILDROOT}
+end
+
+packages
+	package %{name}
+		requires
+			perl
+		end
+	end
+
+	package %{name}-debuginfo
+		template DEBUGINFO
+	end
+end


hooks/post-receive
--
IPFire 3.x development tree

                 reply	other threads:[~2012-01-07 20:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120107200452.81DDB200BA@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox