<big_snip /> My problem still seems unsolved (or did I miss something) ?
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. Do you consider this as stability, seriously ?! cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ --------------------------------------------------------------------- -- gentoo-dev@gentoo.org mailing list
