Summary: | filename collisions | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Paul Thompson <set.mailinglist> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | danarmak, set.mailinglist, vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 3049 |
Description
Paul Thompson
2002-05-19 20:11:03 UTC
Yes, that must the be the source of the problem. Unfortunately I see no good way to deal with it without adding major new functinality to portage. This isn't a common problem but a good case might be made in favour of a generic solution. Maybe something on the order of REMERGE="popt" in the rpm ebuild - you get the idea. A feature proposition might be made, but unfortunately I don't deal in potrage features and don't have any bright ideas about this at present. If you do, they'd be welcome - please open a new bug with any submision, or post on the mailing lists or even ask a dev on irc. A bug about it shouldn't be my property, however, so I'm reassigning it back to bug-wranglers, whence it will probably go to drobbins as a portage feature proposition. Please flesh it out if you can. I Think that there might be a second resolution to this: Check the consistency of the "DEPEND" packages. If any of those packages are "broken" ie, the .so's have the wrong md5 sum or other such thing, then rebuild them, if not, don't rebuild. This will add a sort of "self-healing" feature to portage, instead of blindly forcing a rebuild. Though, a blind force rebuild is a good thing in several cases, fex. "We need python with expat" but depends on Expat + python doesn't rebuild python with expat.... because python is already there. so this might be seen as a partial solution. a simple check + warn might be useful as a first step ... of course a rewrite of the way CONTENTS is stored would be required, i think it might be too slow to parse all the CONTENTS files when merging a new package |