1 |
I'd be interested in at least monitoring the progess of devlopment. I'd |
2 |
love to help out but i'm not sure how much time i have for it, buy hey |
3 |
i'll probly get sucked in after a few emails -=] |
4 |
|
5 |
-- |
6 |
pack |
7 |
|
8 |
On Wed, 2002-02-06 at 11:05, JR Boyens wrote: |
9 |
> Sounds interesting, if your willing to help with an implementation I |
10 |
> would suppose that we could get something together. Let me know on or |
11 |
> off the list and we'll set something up. |
12 |
> |
13 |
> Anyone else interested? |
14 |
> |
15 |
> -- |
16 |
> JR Boyens |
17 |
> jboyens@×××××××.edu |
18 |
> |
19 |
> On Wed, 2002-02-06 at 09:55, Tod M. Neidt wrote: |
20 |
> > Hi! |
21 |
> > |
22 |
> > Was looking at Bug 551 ( http://bugs.gentoo.org/show_bug.cgi?id=551 ) |
23 |
> > this morning. I believe this particular error was generated because the |
24 |
> > user was downloading and install additional perl modules using the |
25 |
> > CPAN.pm module that comes with the perl-5.6.1 package, but didn't have |
26 |
> > the required perl module dependency libnet installed prior to installing |
27 |
> > the telnet module. Info on the CPAN.pm module can be found at |
28 |
> > http://theoryx5.uwinnipeg.ca/CPAN/perl/CPAN.html |
29 |
> > |
30 |
> > Note: I successfully merged the dev-perl/Net-Telnet ebuild using portage |
31 |
> > and the dev-perl/libnet ebuild was merged first like it is supposed to |
32 |
> > so this really isn't a portage or ebuild issue. |
33 |
> > |
34 |
> > However, this situation does bring up an interesting question regarding |
35 |
> > a possible enhancement. |
36 |
> > |
37 |
> > Would it be possible (or even desirable) to hack CPAN.pm and/or portage |
38 |
> > so that they play nice together, i.e. a user could find and download |
39 |
> > perl modules using CPAN.pm and portage would provide the installation |
40 |
> > and package management? |
41 |
> > |
42 |
> > |
43 |
> > Some Advantages: |
44 |
> > |
45 |
> > 1. Useful feature for Gentoo users accustomed to enhancing perl with |
46 |
> > modules through the CPAN.pm module. |
47 |
> > |
48 |
> > 2. Possibility to effectively eleminate the dev-perl portage category, |
49 |
> > while at the same time, (less burden on Gentoo.org servers, and perl |
50 |
> > module ebuild maintainers) |
51 |
> > |
52 |
> > 3. providing *all* the perl modules archived at cpan (the archive) to |
53 |
> > Gentoo users. |
54 |
> > |
55 |
> > 4. Cool hack :) |
56 |
> > |
57 |
> > |
58 |
> > Some Disadvantages: |
59 |
> > |
60 |
> > 1. Extra work maintaining a CPAN.pm-gentoo.diff |
61 |
> > |
62 |
> > 2. perl <--> python interface might be difficult? |
63 |
> > |
64 |
> > 3. package management accounting if both perl module ebuilds and CPAN.pm |
65 |
> > installations are tracked in /var/db/pkg/ |
66 |
> > |
67 |
> > As I am not worthy to wash the feet of a perl deity, I am interested in |
68 |
> > the thoughts of those who are. |
69 |
> > |
70 |
> > tod |
71 |
> > |
72 |
> > |
73 |
> > |
74 |
> > |
75 |
> > _______________________________________________ |
76 |
> > gentoo-dev mailing list |
77 |
> > gentoo-dev@g.o |
78 |
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
79 |
> > |
80 |
> |
81 |
> |
82 |
> |
83 |
> |
84 |
> _______________________________________________ |
85 |
> gentoo-dev mailing list |
86 |
> gentoo-dev@g.o |
87 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |