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