I use Gimp as the example, to show what is the "problem". I have old gimp 1.2.4 installed, and one day I decided to update it.
emerge -p gimp
told me that 1.2.5 was available. I almost started getting it, but then I happened to see www.gimp.org
- the current version was 1.3.21! Oh man! I just did "emerge sync", so why do I have this old version as the "newest"?
Then, I checked what's going on at my harddisk:
locate gimp | grep ebuild
gave me the information of this file:
All right, there it was. An ebuild for the _real_ newest version. But what the heck did those other ebuilds do there?
So, what I'm wondering is: how to tell portage that I do have newer ebuild ready for some package than the one it shows? How to get rid of those old ones, or how at least to let them be old and not show up while updating packages?
Is there a way to clean the older ebuilds away or "hide" them? I thought that "emerge sync" would automatically remove old ebuilds and replace them with the new ones, but it seems like I was wrong...I hope the only way to, as in the example, get the newer version is not to emerge /usr/potage/xxx-xxx/yyy/zzz-a.b.c.ebuild which won't check out dependencies (I guess?).....
-> the thing I'd like to know is how and where is the "newest" package defined..? Is there a file which contains the information of the latest packages?