From: "Kent Fredric" <kentfredric@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/perl-overlay:master commit in: dev-perl/Dancer/
Date: Mon, 25 Feb 2013 08:13:16 +0000 (UTC) [thread overview]
Message-ID: <1361775035.2b027fbb07895b13ee1fc50b34ef9991cf94424c.kent@gentoo> (raw)
commit: 2b027fbb07895b13ee1fc50b34ef9991cf94424c
Author: Kent Fredric <kentfredric <AT> gmail <DOT> com>
AuthorDate: Mon Feb 25 06:50:35 2013 +0000
Commit: Kent Fredric <kentfredric <AT> gmail <DOT> com>
CommitDate: Mon Feb 25 06:50:35 2013 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/perl-overlay.git;a=commit;h=2b027fbb
dev-perl/Dancer , slotify v2 until upstream is obvious
Package-Manager: portage-2.2.0_alpha141
Manifest-Sign-Key: ECD2C675C102CDA4
---
dev-perl/Dancer/ChangeLog | 5 +++++
dev-perl/Dancer/Dancer-2.0.1.ebuild | 2 +-
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/dev-perl/Dancer/ChangeLog b/dev-perl/Dancer/ChangeLog
index 22110df..d201d51 100644
--- a/dev-perl/Dancer/ChangeLog
+++ b/dev-perl/Dancer/ChangeLog
@@ -2,6 +2,11 @@
# Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
+ 25 Feb 2013; Kent Fredric <kentfredric@gmail.com> Dancer-2.0.1.ebuild:
+ Make Dancer v2 a dedicated slot, because upstream have created a confusion,
+ and Dancer >2.0 uses 'Dancer2' as a namespace, and is incompatible with
+ 'Dancer', and Dancer-1.x are still getting releases
+
*Dancer-2.0.1 (23 Feb 2013)
23 Feb 2013; Kent Fredric <kentfredric@gmail.com> +Dancer-2.0.1.ebuild,
diff --git a/dev-perl/Dancer/Dancer-2.0.1.ebuild b/dev-perl/Dancer/Dancer-2.0.1.ebuild
index 16fb1e4..477969d 100644
--- a/dev-perl/Dancer/Dancer-2.0.1.ebuild
+++ b/dev-perl/Dancer/Dancer-2.0.1.ebuild
@@ -8,7 +8,7 @@ inherit perl-module
DESCRIPTION='Lightweight yet powerful web application framework'
LICENSE=" || ( Artistic GPL-2 )"
-SLOT="0"
+SLOT="2"
KEYWORDS="~amd64 ~x86"
IUSE="test"
perl_meta_configure() {
next reply other threads:[~2013-02-25 8:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 8:13 Kent Fredric [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-07 6:51 [gentoo-commits] proj/perl-overlay:master commit in: dev-perl/Dancer/ Kent Fredric
2016-03-07 6:51 Kent Fredric
2014-04-13 5:13 Kent Fredric
2013-12-26 2:12 Kent Fredric
2013-10-11 4:52 Kent Fredric
2013-09-17 4:28 Kent Fredric
2013-05-09 11:44 Kent Fredric
2013-05-03 12:51 Kent Fredric
2013-02-25 8:13 Kent Fredric
2012-10-27 8:36 Kent Fredric
2012-09-15 23:19 Kent Fredric
2012-08-12 12:07 Kent Fredric
2012-07-29 4:22 Kent Fredric
2012-07-20 3:17 Kent Fredric
2012-04-06 20:43 Kent Fredric
2012-03-01 11:37 Kent Fredric
2012-02-08 13:19 Kent Fredric
2012-02-08 13:19 Kent Fredric
2012-02-08 13:19 Kent Fredric
2012-01-24 20:10 Torsten Veller
2012-01-24 20:10 Torsten Veller
2011-12-08 9:30 Kent Fredric
2011-08-26 16:03 Kent Fredric
2011-07-31 10:42 Kent Fredric
2011-07-15 7:11 Kent Fredric
2011-06-29 1:24 Kent Fredric
2011-06-29 1:24 Kent Fredric
2011-05-28 6:12 Torsten Veller
2011-05-28 6:12 Torsten Veller
2011-05-23 5:21 Kent Fredric
2011-05-05 18:16 [gentoo-commits] proj/perl-overlay:perl514 " Kent Fredric
2011-05-05 8:43 ` [gentoo-commits] proj/perl-overlay:master " Kent Fredric
2011-04-13 13:01 Kent Fredric
2011-03-22 1:34 Kent Fredric
2011-03-22 1:34 Kent Fredric
2011-03-14 21:35 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=1361775035.2b027fbb07895b13ee1fc50b34ef9991cf94424c.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