1 |
How about cpan related stuff keep (the .cpan/CPAN .cpan/sources directories), |
2 |
the build and ebuild related we let get wiped (since that's all generated for |
3 |
one time use)? |
4 |
|
5 |
|
6 |
On Sunday 15 May 2005 09:03, Antoine Raillon wrote: |
7 |
> Le dimanche 15 mai 2005 à 08:26 -0400, Michael Cummings a écrit : |
8 |
> > There are arguments for both sides of this one, and I'm completely open. |
9 |
> > Granted, might help if I looked at what it was we were cleaning to see if |
10 |
> > there was anything we could trim out of the routine anyway. Thoughts? |
11 |
> |
12 |
> Well, maybe it's not for now as we're feature freezed, but what about |
13 |
> different default behaviour according to which action is requested ? |
14 |
> for example, after searching we keep the stuff, while after |
15 |
> installing/upgrading we delete it ? |
16 |
> of course, later, we can override both by setting default behaviour in |
17 |
> an external config file.. :) (not very compatible with feature freeze |
18 |
> too ;p) |
19 |
> |
20 |
> -- |
21 |
> cab |
22 |
|
23 |
-- |
24 |
-----o()o--------------------------------------------- |
25 |
Michael Cummings | #gentoo-dev, #gentoo-perl |
26 |
Gentoo Perl Dev | on irc.freenode.net |
27 |
-----o()o--------------------------------------------- |
28 |
|
29 |
-- |
30 |
gentoo-perl@g.o mailing list |