public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kent Fredric" <kentfredric@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/perl-overlay:master commit in: dev-perl/POE-Component-SSLify/
Date: Fri,  3 May 2013 10:51:51 +0000 (UTC)	[thread overview]
Message-ID: <1367575464.126e671f1189c4b0df9d88d79d234d52df6d2f73.kent@gentoo> (raw)

commit:     126e671f1189c4b0df9d88d79d234d52df6d2f73
Author:     Daniel Westermann-Clark <dwc <AT> pobox <DOT> com>
AuthorDate: Sun Apr  4 19:31:25 2010 +0000
Commit:     Kent Fredric <kentfredric <AT> gmail <DOT> com>
CommitDate: Fri May  3 10:04:24 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/perl-overlay.git;a=commit;h=126e671f

Bump dev-perl/POE-Component-SSLify to 0.18
(Portage version: 2.1.7.17/git/Linux x86_64)
 (Signed Manifest commit)

---
 dev-perl/POE-Component-SSLify/ChangeLog            |    8 +++++++-
 ....15.ebuild => POE-Component-SSLify-0.18.ebuild} |    5 +++--
 2 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/dev-perl/POE-Component-SSLify/ChangeLog b/dev-perl/POE-Component-SSLify/ChangeLog
index 155153b..7768db3 100644
--- a/dev-perl/POE-Component-SSLify/ChangeLog
+++ b/dev-perl/POE-Component-SSLify/ChangeLog
@@ -1,7 +1,13 @@
 # ChangeLog for dev-perl/POE-Component-SSLify
-# Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
+# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+*POE-Component-SSLify-0.18 (04 Apr 2010)
+
+  04 Apr 2010; Daniel Westermann-Clark <dwc@pobox.com>
+  -POE-Component-SSLify-0.15.ebuild, +POE-Component-SSLify-0.18.ebuild:
+  Bump dev-perl/POE-Component-SSLify to 0.18
+
 *POE-Component-SSLify-0.15 (08 Jul 2009)
 
   08 Jul 2009; Daniel Westermann-Clark <dwc@pobox.com>

diff --git a/dev-perl/POE-Component-SSLify/POE-Component-SSLify-0.15.ebuild b/dev-perl/POE-Component-SSLify/POE-Component-SSLify-0.18.ebuild
similarity index 78%
rename from dev-perl/POE-Component-SSLify/POE-Component-SSLify-0.15.ebuild
rename to dev-perl/POE-Component-SSLify/POE-Component-SSLify-0.18.ebuild
index 168bf2b..a03e460 100644
--- a/dev-perl/POE-Component-SSLify/POE-Component-SSLify-0.15.ebuild
+++ b/dev-perl/POE-Component-SSLify/POE-Component-SSLify-0.18.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2009 Gentoo Foundation
+# Copyright 1999-2010 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Header: $
 
@@ -15,7 +15,8 @@ KEYWORDS="~amd64 ~x86"
 SRC_TEST="do"
 
 IUSE="test"
-RDEPEND=">=dev-perl/Net-SSLeay-1.30"
+RDEPEND=">=dev-perl/Net-SSLeay-1.36"
 DEPEND="virtual/perl-Module-Build
 	${RDEPEND}
+	>=dev-perl/POE-1.267
 	test? ( virtual/perl-Test-Simple )"


             reply	other threads:[~2013-05-03 10:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 10:51 Kent Fredric [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-14 16:30 [gentoo-commits] proj/perl-overlay:master commit in: dev-perl/POE-Component-SSLify/ Kent Fredric
2015-06-09  8:14 Kent Fredric
2013-05-03 10:51 Kent Fredric
2013-05-03 10:51 Kent Fredric
2013-05-03 10:51 Kent Fredric
2013-05-03 10:51 Kent Fredric
2013-05-03 10:51 Kent Fredric
2013-05-03 10:51 Kent Fredric

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=1367575464.126e671f1189c4b0df9d88d79d234d52df6d2f73.kent@gentoo \
    --to=kentfredric@gmail.com \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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