Summary: | ebuild foo.ebuild compile && ebuild foo.ebuild qmerge fails | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Peter Johanson (RETIRED) <latexer> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | mlspamcb |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Johanson (RETIRED)
2003-07-17 13:28:24 UTC
<bugzilla-troll> bump inactive bug </bugzilla-troll> ebuild .... install is missing...., OTOH, why not let qmerge check for a flag if the product is installed? (like compile & install do w.r.t. unpack & compile). And also let qmerge make a flags to prevent: do ebuild ... qmerge and again: ebuild ... qmerge Chances are the newly installed product becomes UNMERGED. This is still a problem in portage 2.0.50_pre19 |