I already suggested that in bug 28705 but was lacking a real reason back then, now I have one: I have a rsync tree in /usr/portage for normal usage and a cvs tree in /home/gentoo/cvs/gentoo-x86 and a few aliases to work with the cvs tree (cmerge='PORTDIR="/home/gentoo/cvs/gentoo-x86" emerge' and so on). But now whenever I use the cvs tree and the update files are out of sync with the rsync tree (older or newer) they are applied which can be a major annoyance (as when I use the rsync tree they'll be applied again).
backwards/forwards isn't a good reason. If you want to make it account for all portdirs, then feel free.
Created attachment 23654 [details, diff] Patch to compare the update list with already applied updates How about this (checking the actual contents) ? Should also give a nice speedup in general as we don't apply the whole file but only the parts that weren't done in a previous run.
Marius... thoughts on this?
on what?
Anything going on here?
This might not be worth doing anything about now since the global updates code is much more efficient since portage-2.1 or so.
(In reply to comment #6) > This might not be worth doing anything about now since the global updates > code is much more efficient since portage-2.1 or so. Also, you can use --package-moves=n to disable global updates if you want. I set this in EMERGE_DEFAULT_OPTS so that then just use --package-moves=y when I want the moves.
