Re: either/or dependencies breaks show-depends-pkgpaths?

[David Holland <dholland-pkgtech%netbsd.org@localhost>]

On Fri, Jan 17, 2014 at 07:28:18PM -0500, Richard Hansen wrote:
 > > 7. If the package depends on either one of two (or more) packages,
 > >    specify the ?pre-req-package-name? as a comma-separated list between
 > >    curly braces.
 > > 
 > >    As an example, take a package that depends on the Perl "version"
 > >    module, which has been part of Perl itself since version 5.10.0. This
 > >    either/or dependency is expressed as:
 > > 
 > >        DEPENDS+= {perl>=5.10.0,p5-version-[0-9]*}:../../devel/p5-version 
 > 
 > The 'show-depends-pkgpaths' target appears to break on these either/or
 > dependencies:
 > [snip]

I think it's negotiable whether that's actually broken, but it
certainly isn't helpful if you're trying to use the output to plan or
control builds.

One possible way to fix it would be to move it to where it can depend
on the package tools and make it work like show-installed-depends;
that isn't necessarily what one wants though (as the answers will
depend on what's installed)... another is to pass it through something
like reduce-depends.awk, but of course it isn't entirely trivial to do
this reduction. (AFAICT reduce-depends.awk currently doesn't handle
it.) (Also, while this will cover Perl modules it won't work in
general.)

-- 
David A. Holland
dholland%netbsd.org@localhost