From: Patrick Flaherty <patrick_flaherty@c-i-s.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: Perl CPAN.pm and portage (Bug 551 or "Can't we all get along?")
Date: 07 Feb 2002 19:23:05 -0500 [thread overview]
Message-ID: <1013127785.7104.6.camel@intern2.c-i-s.com> (raw)
In-Reply-To: <1013011526.29161.9.camel@fooninja.org>
I'd be interested in at least monitoring the progess of devlopment. I'd
love to help out but i'm not sure how much time i have for it, buy hey
i'll probly get sucked in after a few emails -=]
--
pack
On Wed, 2002-02-06 at 11:05, JR Boyens wrote:
> Sounds interesting, if your willing to help with an implementation I
> would suppose that we could get something together. Let me know on or
> off the list and we'll set something up.
>
> Anyone else interested?
>
> --
> JR Boyens
> jboyens@iastate.edu
>
> On Wed, 2002-02-06 at 09:55, Tod M. Neidt wrote:
> > Hi!
> >
> > Was looking at Bug 551 ( http://bugs.gentoo.org/show_bug.cgi?id=551 )
> > this morning. I believe this particular error was generated because the
> > user was downloading and install additional perl modules using the
> > CPAN.pm module that comes with the perl-5.6.1 package, but didn't have
> > the required perl module dependency libnet installed prior to installing
> > the telnet module. Info on the CPAN.pm module can be found at
> > http://theoryx5.uwinnipeg.ca/CPAN/perl/CPAN.html
> >
> > Note: I successfully merged the dev-perl/Net-Telnet ebuild using portage
> > and the dev-perl/libnet ebuild was merged first like it is supposed to
> > so this really isn't a portage or ebuild issue.
> >
> > However, this situation does bring up an interesting question regarding
> > a possible enhancement.
> >
> > Would it be possible (or even desirable) to hack CPAN.pm and/or portage
> > so that they play nice together, i.e. a user could find and download
> > perl modules using CPAN.pm and portage would provide the installation
> > and package management?
> >
> >
> > Some Advantages:
> >
> > 1. Useful feature for Gentoo users accustomed to enhancing perl with
> > modules through the CPAN.pm module.
> >
> > 2. Possibility to effectively eleminate the dev-perl portage category,
> > while at the same time, (less burden on Gentoo.org servers, and perl
> > module ebuild maintainers)
> >
> > 3. providing *all* the perl modules archived at cpan (the archive) to
> > Gentoo users.
> >
> > 4. Cool hack :)
> >
> >
> > Some Disadvantages:
> >
> > 1. Extra work maintaining a CPAN.pm-gentoo.diff
> >
> > 2. perl <--> python interface might be difficult?
> >
> > 3. package management accounting if both perl module ebuilds and CPAN.pm
> > installations are tracked in /var/db/pkg/
> >
> > As I am not worthy to wash the feet of a perl deity, I am interested in
> > the thoughts of those who are.
> >
> > tod
> >
> >
> >
> >
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> >
>
>
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-02-08 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 15:55 [gentoo-dev] RFC: Perl CPAN.pm and portage (Bug 551 or "Can't we all get along?") Tod M. Neidt
2002-02-06 16:05 ` JR Boyens
2002-02-08 0:23 ` Patrick Flaherty [this message]
2002-02-10 6:46 ` JR Boyens
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=1013127785.7104.6.camel@intern2.c-i-s.com \
--to=patrick_flaherty@c-i-s.com \
--cc=gentoo-dev@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