10320 – ebuilds merged by filename are not added to world file

Bug 10320 - ebuilds merged by filename are not added to world file

Summary: ebuilds merged by filename are not added to world file

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	Inclusion

Depends on:
Blocks:

Reported:	2002-11-06 02:57 UTC by J Robert Ray
Modified:	2011-10-30 22:19 UTC (History)
CC List:	4 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Patch (emerge_10320,541 bytes, patch) 2003-09-14 21:58 UTC, Carlos Castillo	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description J Robert Ray 2002-11-06 02:57:42 UTC

... and end up tagged for removal by depclean.

Comment 1 Charles Goodwin 2003-09-09 09:26:11 UTC

It could be even more serious than that.

All the programs that I'm emerging by 'emerge /usr/portage/cat/app/app-ver.ebuild' are not being added to the world file either and hence end up tagged for removal by depclean.

Comment 2 Carlos Castillo 2003-09-14 21:58:14 UTC

Created attachment 17740 [details, diff]
Patch

This patch solves the situation you describe. However I don't know if it is a
bug or not.

Comment 3 Marius Mauch (RETIRED) gentoo-dev

2003-10-09 14:56:17 UTC

PORTDIR_OVERLAY packages are added to the world file, so this part can be
closed.
Nick, is the non-adding of packages installed with `emerge /path/to/ebuild`
a bug or not?

Comment 4 Martin Holzer (RETIRED) gentoo-dev

2003-10-13 13:19:01 UTC

seems to be a bug
installed package should be added in db.

Comment 5 Nicholas Jones (RETIRED) gentoo-dev

2004-01-19 17:20:06 UTC

They are in the DB... They aren't added to a list of packages to be
considered as starting nodes for world though.

If you take the time to force portage to merge a package by giving
it the filename of the package, bypassing all checks, there is
absolutely no reason for portage to assume that you want it to
take over from that point on.

So it's left to the user... either be anal and deal with it, or
stop making things difficult.