The 'world' file has a tendency to go wrong, that means it does not reflect what's actually in my system. Although you may say this is my fault, since I am not the only one who has trouble here and perhaps a lot of users are unaware of the problem, I suggest the following improvements: [1] option for emerge to work on all packages in update mode instead of the world file [2] world file should be sorted for easier comparing [3] equery could have an option to output world file with all packages [4] world file could be automatically backed up whenever there is a change during emerge Reproducible: Always
(In reply to comment #0) > The 'world' file has a tendency to go wrong, that means it does not reflect > what's actually in my system. Although you may say this is my fault, since I am > not the only one who has trouble here and perhaps a lot of users are unaware of > the problem, I suggest the following improvements: World file only lists what you've directly emerged (unless you've used --oneshot) - not any direct or inderect dependencies; that's a feature and not a bug. Use emerge --noreplace if you want to add stuff to world for whatever reason. > [1] option for emerge to work on all packages in update mode instead of the > world file Dupe of Bug 6411 > [2] world file should be sorted for easier comparing cat /var/lib/portage/world | sort -d > [3] equery could have an option to output world file with all packages Hmmm? What exactly would it do?
(In reply to comment #0) > [1] option for emerge to work on all packages in update mode instead of the > world file bug 96088 > [2] world file should be sorted for easier comparing Will do. Also, we'll add a newline to the end (bug 151364). > [3] equery could have an option to output world file with all packages I think it would be reasonable to make that an option of emerge itself. It could list any of the sets that it knows about (system, world, and more in the future). > [4] world file could be automatically backed up whenever there is a change > during emerge If you have problems with missing entries, it's probably because you run parallel emerge instances. I'm planning to fix that as part of bug 147516.
1) and 3) fall under generic set support, 4) is pointless IMO: either we'd keep a very high number of backups (>=10) or it's likely that all backups would be overwritten before a potential problem is discovered. Leaves only 2), which is now in trunk.
This has been released in 2.1.3_rc6.
