Gentoo Archives: gentoo-perl

From: Michael Cummings <mcummings@g.o>
To: gentoo-perl@l.g.o
Subject: Re: [gentoo-perl] Fwd: Réf. : Re: g-cpan ;)
Date: Wed, 11 May 2005 08:40:50
Message-Id: 200505110440.54368.mcummings@gentoo.org
In Reply to: Re: [gentoo-perl] Fwd: Réf. : Re: g-cpan ;) by Antoine Raillon
1 On Tuesday 10 May 2005 07:49 pm, Antoine Raillon wrote:
2 > Well, ok, let's keep it ;)
3 > It has to be cleaned however ;p
4 > and the --list should also be available (it's probably almost the same
5 > code however ;p)
6
7 Totally agree.
8 >
9 > Well my original idea was to avoid new downloads each time you run
10 > g-cpan as user to do search. I admit it's a very specific case ;p
11 > Sniper tried to convince me I was wrong, but i'm not totally convinced
12 > yet ;p
13
14 Ah, but if we just avoid cleaning out .cpan, that will cover it. By cleaning
15 out .cpan each run, we wipe the downloaded files that CPAN uses to do the
16 searches. By not deleting them, CPAN checks for their existence and only
17 downloads new ones (the modulelist, etc.) if their time stamp is too old.
18
19 >
20 > We support them for searches only ;)
21 > I'd prefer if this file was system-wide, I just think it's the way it
22 > should be =)
23
24 Actually - that's not true. Any user under the current code can initiate any
25 g-cpan function, not just searches. And this has advantages, too - if you
26 have configured box to allow members of the portage group to do userpriv
27 emerges, then any user who is a member of groups:portage should be allowed to
28 use g-cpan as well (as they can in the last version of 0.13 I looked at). To
29 boot, a user can append to the overlay listing (I know I do on my local boxes
30 - mcummings has a huge list of overlay dirs compared to root has none) via an
31 environment variable. Plus...I'm drawing a blank on what would go in this
32 config file right now. I can envision in >0.13 including some nifty logging
33 facilities (needed!), but beyond a few config vars related to that I can't
34 come up with anything that you'd want to config (throw me a line here :) )
35
36 >
37 > > >- a special sub for md5ing things ? ($md5 = md5-sum($file)). It would
38 > > > clean some lines ;)
39 >
40 > I've done this one tonight
41
42 sweet :)
43
44 > > as well as the whole scanning the tree parts :)
45 >
46 > Tomorrow maybe ? but your code is dense and i don't fully understand
47 > it ;)
48 > /me refuses to broke anything ;p
49
50 Bah, my code is child's play compared to regex-King's stuff ;)
51
52 > > >- updating exit_usage ;p
53 > >
54 > > yeah - thinking we might not want to remove the generated config for
55 > > cpan, just tell them its there and they can fix it if they want better
56 > > performance
57 >
58 > and checking for what will stay in those ./cpan dirs too (especially if
59 > we use them as local overlays ;p)
60
61 See comments above - I agree (anyone else want to weigh in?)
62
63 > Sniper had some other ideas, but i'll let him introduce them ;)
64 Isn't step one getting sniper on a gentoo box first ? ;) (j/k)
65
66 --
67
68 -----o()o---------------------------------------------
69 Michael Cummings | #gentoo-dev, #gentoo-perl
70 Gentoo Perl Dev | on irc.freenode.net
71 -----o()o---------------------------------------------

Replies

Subject Author
Réf. : Re: [gentoo-perl] Fwd: Réf. : Re: g-cpan ;) antoine.raillon@××××.com