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

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

[pclouds]

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?
-- 
Bi Cờ Lao

-- 
gentoo-dev@gentoo.org mailing list

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

[Krzysiek Pawlik]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

pclouds wrote:
> This is an idea. Currently, after an ebuild is merged into system. I
> have no idea where that ebuild comes from.

Use emerge:

nelchael@nelchael ~$ emerge -pv resin

These are the packages that I would merge, in order:

Calculating dependencies  ...done!
[ebuild   R   ] www-servers/resin-3.0.13  0 kB [2]
                                              ^^^^^
Total size of downloads: 0 kB
Portage overlays:
 [1] /usr/local/portage/devel
 [2] /usr/local/portage/java
 [3] /usr/local/portage/my
nelchael@nelchael ~$

It informs whenever this ebuild comes from main portage tree, or from
overlay (and from which overlay).

- --
Krzysiek 'Nelchael' Pawlik    RLU #322999    GPG:0xBC555551
gentoo - kernel 2.6.xx + CK patchset
http://fatcat.ftj.agh.edu.pl/~nelchael/
'Calm down -- it's only ones and zeros.'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDHA5rgo/w9rxVVVERAqidAKCxDTCJl7uPzG8SkpAPB8zd3CyoSQCgjr25
WFxIz8uuyhT8vLd7uYoPx3Q=
=pF26
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

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

[Jason Stubbs]

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[pclouds]

On 9/5/05, Jason Stubbs <jstubbs@gentoo.org> wrote:
> The gentoo-portage-dev@g.o mailing list would be better for this type of
> query...
Ok. I'll stop by gentoo-portage-dev next time :)

> 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.

There is another use. When report bugs to b.g.o, gentoo devs only take
care of bugs that all dependencies are come from the main tree. Users
mixed their environment with other overlays should check all
dependencies before submitting to b.g.o or bugs will be resolved as
wontfix. In case users use overlays, users would know what overlay
ebuilds come from and contact overlays' authors instead of b.g.o. Not
a big advantage though.
-- 
Bi Cờ Lao

-- 
gentoo-dev@gentoo.org mailing list

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

[Jason Stubbs]

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

On Monday 05 September 2005 21:15, pclouds wrote:
> On 9/5/05, Jason Stubbs <jstubbs@gentoo.org> wrote:
> > The gentoo-portage-dev@g.o mailing list would be better for this type
> > of query...
>
> Ok. I'll stop by gentoo-portage-dev next time :)
>
> > 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.
>
> There is another use. When report bugs to b.g.o, gentoo devs only take
> care of bugs that all dependencies are come from the main tree. Users
> mixed their environment with other overlays should check all
> dependencies before submitting to b.g.o or bugs will be resolved as
> wontfix. In case users use overlays, users would know what overlay
> ebuilds come from and contact overlays' authors instead of b.g.o. Not
> a big advantage though.

It is in automation. :)

Automated bug reports has been an idea that's been thrown around a bit. This 
would help prevent "spam" from getting through too. I'm beginning to like 
the idea more and more. ;)

-- 
Jason Stubbs

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]