Gentoo Archives: gentoo-dev

From: JR Boyens <jboyens@××××××××.org>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] RFC: Perl CPAN.pm and portage (Bug 551 or "Can't we all get along?")
Date: Sun, 10 Feb 2002 00:52:21
Message-Id: 1013323611.23517.7.camel@fooninja.org
In Reply to: Re: [gentoo-dev] RFC: Perl CPAN.pm and portage (Bug 551 or "Can't we all get along?") by Patrick Flaherty
1 Currently the best option I'm seeing is to write a ebuild script for
2 each module you want. Say you want CGI::Bob something like:
3 src_compile () { perl -MCPAN -e 'make CGI::Bob' }
4 src_install () { perl -MCPAN -e 'install CGI::Bob' }
5 Unfortuately since there is no tarball for portage to get, we would have
6 to either fake it out with a 'blank' tarball or change portage's
7 behavior.
8
9 Creating the actual ebuilds are completely easy with a perl script that
10 whips through CPAN... Hmmm thinking as I write this adding a --perl or
11 some special dev-perl handling to emerge so that emerge executes the
12 CPAN install would work even better.....
13
14 Any suggestions?
15 --
16 JR Boyens
17 jboyens@×××××××.edu
18
19 On Thu, 2002-02-07 at 18:23, Patrick Flaherty wrote:
20 > I'd be interested in at least monitoring the progess of devlopment. I'd
21 > love to help out but i'm not sure how much time i have for it, buy hey
22 > i'll probly get sucked in after a few emails -=]
23 >
24 > --
25 > pack
26 >
27 > On Wed, 2002-02-06 at 11:05, JR Boyens wrote:
28 > > Sounds interesting, if your willing to help with an implementation I
29 > > would suppose that we could get something together. Let me know on or
30 > > off the list and we'll set something up.
31 > >
32 > > Anyone else interested?
33 > >
34 > > --
35 > > JR Boyens
36 > > jboyens@×××××××.edu
37 > >
38 > > On Wed, 2002-02-06 at 09:55, Tod M. Neidt wrote:
39 > > > Hi!
40 > > >
41 > > > Was looking at Bug 551 ( http://bugs.gentoo.org/show_bug.cgi?id=551 )
42 > > > this morning. I believe this particular error was generated because the
43 > > > user was downloading and install additional perl modules using the
44 > > > CPAN.pm module that comes with the perl-5.6.1 package, but didn't have
45 > > > the required perl module dependency libnet installed prior to installing
46 > > > the telnet module. Info on the CPAN.pm module can be found at
47 > > > http://theoryx5.uwinnipeg.ca/CPAN/perl/CPAN.html
48 > > >
49 > > > Note: I successfully merged the dev-perl/Net-Telnet ebuild using portage
50 > > > and the dev-perl/libnet ebuild was merged first like it is supposed to
51 > > > so this really isn't a portage or ebuild issue.
52 > > >
53 > > > However, this situation does bring up an interesting question regarding
54 > > > a possible enhancement.
55 > > >
56 > > > Would it be possible (or even desirable) to hack CPAN.pm and/or portage
57 > > > so that they play nice together, i.e. a user could find and download
58 > > > perl modules using CPAN.pm and portage would provide the installation
59 > > > and package management?
60 > > >
61 > > >
62 > > > Some Advantages:
63 > > >
64 > > > 1. Useful feature for Gentoo users accustomed to enhancing perl with
65 > > > modules through the CPAN.pm module.
66 > > >
67 > > > 2. Possibility to effectively eleminate the dev-perl portage category,
68 > > > while at the same time, (less burden on Gentoo.org servers, and perl
69 > > > module ebuild maintainers)
70 > > >
71 > > > 3. providing *all* the perl modules archived at cpan (the archive) to
72 > > > Gentoo users.
73 > > >
74 > > > 4. Cool hack :)
75 > > >
76 > > >
77 > > > Some Disadvantages:
78 > > >
79 > > > 1. Extra work maintaining a CPAN.pm-gentoo.diff
80 > > >
81 > > > 2. perl <--> python interface might be difficult?
82 > > >
83 > > > 3. package management accounting if both perl module ebuilds and CPAN.pm
84 > > > installations are tracked in /var/db/pkg/
85 > > >
86 > > > As I am not worthy to wash the feet of a perl deity, I am interested in
87 > > > the thoughts of those who are.
88 > > >
89 > > > tod
90 > > >
91 > > >
92 > > >
93 > > >
94 > > > _______________________________________________
95 > > > gentoo-dev mailing list
96 > > > gentoo-dev@g.o
97 > > > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
98 > > >
99 > >
100 > >
101 > >
102 > >
103 > > _______________________________________________
104 > > gentoo-dev mailing list
105 > > gentoo-dev@g.o
106 > > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
107 >
108 >
109 > _______________________________________________
110 > gentoo-dev mailing list
111 > gentoo-dev@g.o
112 > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
113 >