Re: [gentoo-dev] Keep track what ebuild comes from what repository

[Jason Stubbs]

On Monday 05 September 2005 18:06, pclouds wrote:
> This is an idea. Currently, after an ebuild is merged into system. I
> have no idea where that ebuild comes from. I think we should keep the
> the ebuild's repository signature  in /var/db/pkg. When thing's
> broken, i may find out where to find the original ebuild and fix it
> (is it in official portage tree, or is it my overlay?). Of course we
> need a signature for each repositories. Don't know how to make
> signatures, how to implement it in portage though. Any thoughts?

The gentoo-portage-dev@g.o mailing list would be better for this type of 
query...

Tagging overlays into the vdb metadata is easy enough, but does it actually 
provide any usefulness other than to track down a source that may no longer 
exist? I assume if you're having trouble finding a package that you must 
have several overlays that you sync from external sources.

Actually, there is a use. Presently, if your overlay has foo/bar-1.0 and the 
main tree as foo/bar-1.1 you'll get the main tree's later version installed 
even if you installed foo/bar-1.0 from your overlay. In my experience, this 
is almost never what is actually wanted.

-- 
Jason Stubbs