On Mon, 2006-08-07 at 15:01 +0200, Enrico Weigelt wrote: > Lets say, if I've, installed foo-1.1, and it gets masked due > some bug(s), but 1.0 isn't, I want to get informed with an big > fat warning, *before* anything actually done, ie. > > [...] > # WARNING: installed package foo-1.1 has been masked and would > # be downgraded: > # <masking comment ...> > [...] > > An fully-automatic downgrade should *never* downgrade anything. > This is too dangerous, because essential features can get lost. > Again, my bugzilla example: assuming 2.22 will be unmasked some > day and I installed it w/ postgres support. Now there are some > bugs found, but not fixed fast enough, so it gets masked. > I run an update w/o knowing that it downgrades, and my whole > bugzilla hosting is suddenly broken.
That would not happen. bugzilla is a webapp and as such is fully SLOTted. Upgrades (and downgrades) are manual. Ed -- gentoo-dev@gentoo.org mailing list
