From: Michele Beltrame <admin@talkblade.info>
To: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] Catalyst in the main portage tree
Date: Tue, 21 Nov 2006 00:47:53 +0100 [thread overview]
Message-ID: <1164066473.18104.10.camel@nowhere.italpro.to> (raw)
Message-ID: <20061120234748.595047@smtpi2.ngi.it> (raw)
In-Reply-To: <200611200809.41368.mcummings@gentoo.org>
Hello!
The inclusion of Catalyst in the main Gentoo repository would be
fantastic! The overlay is currently made of 156 ebuilds; not necessarly
all of them have to make it into portage, but I think at least the ones
most widely used by Catalyst users should. So, probably at least
100-120. Yeah, I now it's a scary amount of ebuilds... ;-)
An important aspect will be the contact between the Catalyst community
and the Gentoo Perl herd - that is, between me and the future maintainer
of the ebuilds. Fact is in the Catalyst world things evolve sometimes
quickly, so new modules (=>ebuilds) are added, other are deprecated,
etc. It's now quite easy for me to keep the unofficial overlay
up-to-date, as I'm into the Catalyst community; when (if) it'll go into
portage, I guess I won't be the one to maintain the thing, but I'll be
sure to "haunt" the maintainer (Antoine? ;-)) when things need to be
changed.
Also, if you decide to make this thing I'll need to check all the
ebuilds as some are missing the LICENSE line, and some descriptions are
er... not so up-to-date. ;-)
I hope Catalyst will get this important chance to see its user base
grow!
Michele.
--
gentoo-perl@gentoo.org mailing list
prev parent reply other threads:[~2006-11-20 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 13:09 [gentoo-perl] Catalyst in the main portage tree Michael Cummings
2006-11-20 15:02 ` Antoine Raillon
[not found] ` <20061120234748.595047@smtpi2.ngi.it>
2006-11-20 23:47 ` Michele Beltrame [this message]
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=1164066473.18104.10.camel@nowhere.italpro.to \
--to=admin@talkblade.info \
--cc=gentoo-perl@gentoo.org \
--cc=gentoo-perl@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