Dnia 2014-07-26, o godz. 14:02:29 Martin Vaeth <mar...@mvath.de> napisał(a):
> Alexandre Rostovtsev <tetrom...@gentoo.org> wrote: > > > > rdepends-add is easy to implement [...] Deletion is trickier [...] > > > > The point is to *not* clean up these entries for months/years. > > So, essentially, you want the developer to do part of CVS/git's job, > namely keeping a history of changes in a compressed format, > keeping the history forever (or almost forever). > As mentioned in another post, you highly understimate the > amount of data which would have to be treated this way: > For every python release and many other eclass changes, > almost all packages in the tree are involved, usually > several times a months. Python is irrelevant here. Our dependencies are USE-conditional, so dependencies are added and removed along with USE flags. If we add new implementation, you need to rebuild the package anyway to use it, and there is no point populating extra dependencies. Revbump isn't necessary either since --changed-use will pick it up if necessary. If we remove an implementation, PM isn't supposed to remove the dependencies until the package is rebuilt with flag disabled. If it was enabled, --changed-use is supposed to clean it up. If it was not, the extra dependencies do not matter (and are not even stored in vdb). -- Best regards, Michał Górny
signature.asc
Description: PGP signature
