1 |
On Mon, 24 Jun 2013 09:27:10 -0700 |
2 |
Greg KH <gregkh@g.o> wrote: |
3 |
|
4 |
> On Sat, Jun 22, 2013 at 08:45:25AM +0200, Tom Wijsman wrote: |
5 |
> True, so we can keep around 3-4 older ebuilds if needed, per kernel |
6 |
> release. But who really does a dependency clean these days, I've |
7 |
> never done one :) |
8 |
|
9 |
Depends a bit on your workflow; in my case, I ... |
10 |
|
11 |
1) Update my system on a daily basis. |
12 |
2) Test many packages I don't actively use, typical on some herds. |
13 |
3) Test many kernels, each having their own slot; leaving stuff behind. |
14 |
4) Randomly emerge interesting software to try it; I usually do this |
15 |
with -1 so I don't forget to unmerge them, supposing I dep clean. |
16 |
|
17 |
Especially those cases where there are dependency changes (whether |
18 |
the dependency is no longer used or the slot changed) a lot of |
19 |
dependencies (and some packages) can be left behind. |
20 |
|
21 |
So, I do have to run it now and then or it will clog my system; not to |
22 |
forget about the many other non Portage creep that could fill up. |
23 |
|
24 |
> So, what's the next step? Should I announce the change to -dev? |
25 |
|
26 |
I wonder if a news item is in place for this change, because we will |
27 |
be dropping all stable keywords. If I remember correctly news items |
28 |
have to pass the -dev ML. On the other hand, I don't really have an |
29 |
idea of how important this issue is to be considered; though it may be |
30 |
handy to err on the side of being more transparent towards our users. |
31 |
|
32 |
> Anyone else really object to it? Other thoughts? |
33 |
|
34 |
I thought the idea of not stabilizing worked out the best, dropping |
35 |
insecure and EOL versions and keeping the versions from the last month |
36 |
of each branch around or so (we do this very last thing on g-s too). |
37 |
|
38 |
No objections from me. |
39 |
|
40 |
-- |
41 |
With kind regards, |
42 |
|
43 |
Tom Wijsman (TomWij) |
44 |
Gentoo Developer |
45 |
|
46 |
E-mail address : TomWij@g.o |
47 |
GPG Public Key : 6D34E57D |
48 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |