i'm using some unstable packages(mozilla 1.2.1, dvdrip 0.46, ...), but the rest of the system should stay stable. now, if i emerge these unstable packages (ACCEPT_KEYWORD="~x86") and switch back to the stable options (ACCEPT_KEYWORD="") and then run 'emerge -u world' portage wants to replace the unstable by stable ones again! so, 2 ideas from me: 1. make than behavior optional (you can choose if newer packages should be replaced) 2. secont list for packages masks: unmasklist! (if you put '>=mozilla-1.2.1' in here portage will unmask it after it was masked because of the masklist) number 2 is my favourite one :D some notes to this problem: sometimes you have to install masked packages bacouse cou get an error when using 'emerge -u world' because one packeges that needs to be updated depends one another package that is masked --> portage stops running without ANY update so you need to install that needed package yourself and after that the package that is not working...then 'emerge -u world' works again
beryllium ratpoison # emerge -up --deep world [...] [ebuild UD] net-ftp/lftp-2.6.2 [2.6.3-r0] [ebuild U ] sys-apps/util-linux-2.11y [2.11u-r0] [ebuild UD] net-www/links-2.1_pre3 [2.1_pre6-r0] [ebuild U ] sys-apps/net-tools-1.60-r5 [1.60-r4] [ebuild UD] net-irc/irssi-0.8.5-r2 [0.8.6-r0] [ebuild UD] net-fs/nfs-utils-0.3.3-r1 [1.0.1-r0] [ebuild UD] app-misc/screen-3.9.11-r3 [3.9.13-r0] issue: I merged some apps from the unstable tree but I do not want portage to downgrade them when updating world. my solution: -u world should upgrade all the ebuild ("U") but those marked for downgrade ("UD") unless you supply "--all". last thing: shouldn't ebuilds merged from the unstable tree be considered by --depclean ?
err, please ignore my "last thing" in the previous comment.
yours solution is the first idea from me.... but i think the second one is more usefull: if you put ">=mozilla-1.2.1" in that unmasklist your get all the updates, too. (if you do a "emerge -pu world") --> unmasklist must stay if you do a "emerge rsync" perhaps the best is to combine these 2 ideas ;)
Moreover, emerge -up --deep world [...] [ebuild U ] sys-apps/net-tools-1.60-r5 [1.60-r4] [ebuild UD] net-irc/irssi-0.8.5-r2 [0.8.6-r0] [ebuild UD] sys-apps/hdparm-5.2-r3 [5.3-r1] [ebuild U ] sys-apps/quota-3.06 [3.03-r0] [ebuild UD] net-fs/nfs-utils-0.3.3-r1 [1.0.1-r0] It would be great if emerge could distinguish between ebuilds that need/ask to be downgraded: 1) because something went wrong and devs resurrected a previous version. this should be marked "D" (downgrade) (for example, the sys-apps/hdparm above ) 2) because I'm using foo-1.0 from the testing/unstable tree. this should be marked with a "~D" (for example net-irc/irssi above ) or maybe using different colors ... - j2
perhaps it's a good idea to use 3 different package marks instead of 2: stable (default), unstable (if you want), devel/broken (for developers only, new)
*** This bug has been marked as a duplicate of 9379 ***
