| Summary: | ebuilds merged by filename are not added to world file | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | J Robert Ray <jrray> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | carlos, h3y, mholzer, pythonhead |
| Priority: | High | Keywords: | Inclusion |
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Patch | ||
|
Description
J Robert Ray
2002-11-06 02:57:42 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. 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.
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? seems to be a bug installed package should be added in db. 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. |
