On Sat, Apr 30, 2011 at 02:42:08PM +0100, Markos Chandras wrote: > I am actually with Samuli on this. Unless there is a particular reason > for removing a package, I don't see any point of documenting this change > anywhere. > What difference would it make to you if you see an entry " -foo-1.0 > old". It makes absolutely no sense.
Removing versions has implications for the depgraph which make having it documented locally fairly required. Broken dependencies is the usual example, (consider developmental profiles), but it gets nastier than that; consider a pkg depping on || ( =foo-1.0 !block-some-other-crap ) Yes that's a screwed up dep, but people come up with some weird stuff- the point either way is that removal of 1.0 can have implications beyond just the perceived cleanup. Usage of --force in conjunction with it makes it worse. Not opposed to pruning the logs (every few years we seem to go cleanup the offenders), but removals *matter* for the depgraph, thus have been required to be documented long term. ~harrng
pgpxUiuOn97nG.pgp
Description: PGP signature
