I looked through the portage docs but couldn't find a good definition of what the "world" file is.
There's one in /var/lib/portage/world and one in /var/cache/edb/world. What is the difference?
When I do an emerge -up world, is this file referenced somehow?
If I delete it, what happens? Can I rebuild it?
Just curious. I read somewhere that doing a qpkg -nc -I (qpkg is deprecated now, I know) into the world file and then an emerge -u world updates more packages...I don't really understand why that is.
What exactly is the "world" file?
Message
The world file stores the packages which you have installed (emerged) yourself as opposed to any packages that were installed through dependencies. The file /var/lib/portage/world is the actual world file; /var/cache/edb/world is the old location used in previous versions of portage (as far as I know, you can delete this file).
If you do 'emerge -u world' the packages in your world file will be updated with possible new (stable) versions. In the process, any required dependencies will also be pulled in. Any other dependencies will not be updated however, even when there are more recent (stable) versions in portage. For this you can use 'emerge -u --deep world'.
You'll understand that it would not be wise to delete the world file.
In some cases, however, you can delete single entries from the file if you want to speed things up by keeping your world file as small as possible. (For example: if you have done 'emerge digikam digikamimageplugins', both packages will be in your world file. But in fact only digikamimageplugins is required because it depends on digikam.) But unless you absolutely know what you're doing, I advise you to stay away from the world file.
If you do 'emerge -u world' the packages in your world file will be updated with possible new (stable) versions. In the process, any required dependencies will also be pulled in. Any other dependencies will not be updated however, even when there are more recent (stable) versions in portage. For this you can use 'emerge -u --deep world'.
You'll understand that it would not be wise to delete the world file.
In some cases, however, you can delete single entries from the file if you want to speed things up by keeping your world file as small as possible. (For example: if you have done 'emerge digikam digikamimageplugins', both packages will be in your world file. But in fact only digikamimageplugins is required because it depends on digikam.) But unless you absolutely know what you're doing, I advise you to stay away from the world file.Gentoo (64 bits) on AMD64 X2 4400+, MSI K8T Neo2-FIR, 2 Gb RAM, 320 + 160 Gb SATA, nVidia Geforce 6600
So, thanks.Well, if you just do an 'emerge -u world', it will have to check less packages. That will not be the cause of a major speedup of an emerge-cycle, but it may be of use to some people. There may also be some speedups 'under the hood' of portage, but I wouldn't know.Eidi wrote:How would keeping your world file as small as possible speed portage up?
Gentoo (64 bits) on AMD64 X2 4400+, MSI K8T Neo2-FIR, 2 Gb RAM, 320 + 160 Gb SATA, nVidia Geforce 6600
Basically just dependancy checking. I wouldn't go hand editing the world file unless you're certain you know what you're doing. I have been known to, but it took a while before I was comfortable enough to do so.
Other thing is, there may be some packages that are in there (you explicitly emerged), but are both dependancies of something else you have installed & you're not too bothered about being up to date with it. Most people do an 'emerge --deep --update world' or equivalent much less often than a simple 'emerge --update world' - so the second command would be a lot 'lighter' with a smaller world file. No real effect on the first command.
Also don't remove world file entries for anything you need/want to keep unless something else depends on it & will stay on your system! Otherwise you could end out in a sticky situation after a --depclean.
Other thing is, there may be some packages that are in there (you explicitly emerged), but are both dependancies of something else you have installed & you're not too bothered about being up to date with it. Most people do an 'emerge --deep --update world' or equivalent much less often than a simple 'emerge --update world' - so the second command would be a lot 'lighter' with a smaller world file. No real effect on the first command.
Also don't remove world file entries for anything you need/want to keep unless something else depends on it & will stay on your system! Otherwise you could end out in a sticky situation after a --depclean.