Gentoo Archives: gentoo-dev

From: Jason Stubbs <jstubbs@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Keep track what ebuild comes from what repository
Date: Mon, 05 Sep 2005 11:05:23
In Reply to: [gentoo-dev] Keep track what ebuild comes from what repository by pclouds
1 On Monday 05 September 2005 18:06, pclouds wrote:
2 > This is an idea. Currently, after an ebuild is merged into system. I
3 > have no idea where that ebuild comes from. I think we should keep the
4 > the ebuild's repository signature in /var/db/pkg. When thing's
5 > broken, i may find out where to find the original ebuild and fix it
6 > (is it in official portage tree, or is it my overlay?). Of course we
7 > need a signature for each repositories. Don't know how to make
8 > signatures, how to implement it in portage though. Any thoughts?
10 The gentoo-portage-dev@g.o mailing list would be better for this type of
11 query...
13 Tagging overlays into the vdb metadata is easy enough, but does it actually
14 provide any usefulness other than to track down a source that may no longer
15 exist? I assume if you're having trouble finding a package that you must
16 have several overlays that you sync from external sources.
18 Actually, there is a use. Presently, if your overlay has foo/bar-1.0 and the
19 main tree as foo/bar-1.1 you'll get the main tree's later version installed
20 even if you installed foo/bar-1.0 from your overlay. In my experience, this
21 is almost never what is actually wanted.
23 --
24 Jason Stubbs


Subject Author
Re: [gentoo-dev] Keep track what ebuild comes from what repository pclouds <pclouds@×××××.com>