Re: [Discuss-gnuradio] How does 'make check' find its dependencies?

[Greg Troxel]

How will the new structure affect upcoming releases?  NetBSD pkgsrc
currently builds separate packages for each GNU Radio component, which
lets one install them separately and also avoid dependencies for
things you don't need.  Will this just be 'make dist' and a single
tarball?

pkgsrc, unlike some linux packaging systems, doesn't do a single build
and then pick out files for sub-packages - each package has a build
stage.   Sometimmes larged packages are patched (in Makefiles) to
split them, but it's much nicer if the upstream package itself can be
made to install only the right bits (in a mutually exclusive and
jointly exhaustive way).

really minor, but perhaps worth mentioning:

While I see the appeal of omitting things that don't have satisfied
dependencies, that's a bit awkward for a package system which intends
to produce repeatable builds.  (Of course, the dependencies are
recorded so they will be satisfied.)  From that point of view, it
would be nice to be able to enable and disable components and cause
configure to fail if the dependencies are not satisfied.  The default
behavior if not given --enable-foo can of course be
build-if-prereqs-ok.

-- 
    Greg Troxel <address@hidden>

pgpKy6ECicKPt.pgp
Description: PGP signature