On 08/17/2011 10:03 AM, Michał Górny wrote: > On Wed, 17 Aug 2011 10:19:06 +0200 > Ulrich Mueller <[email protected]> wrote: > >>>>>>> On Wed, 17 Aug 2011, Michał Górny wrote: >> >>> And isn't a random PROPERTIES value more fragile? If someone uses it >>> incorrectly, the results are undefined. With older PMs, results are >>> undefined. >> >>> While having empty SRC_URI and no DEFINED_PHASES guarantees that >>> the ebuild won't install a file. That's just per-def, nothing can >>> happen. >> >> Unfortunately, the inverse is not true. There are virtuals that >> define phase functions, see virtual/ruby-* for example. > > And that's another issue in the ebuild. It should be fixed so that > phase functions won't be exported in the first place rather than > redefining them. This way, PM could assume it doesn't need to execute > those at all rather than running dummy code.
You can insist on this SRC_URI + DEFINED_PHASES approach, but I doubt that package manager developers will want to rely on these kinds of fragile assumptions. You thought that relying on the "virtual" category name was ridiculous, but this SRC_URI + DEFINED_PHASES approach seems must less practical to me. -- Thanks, Zac
