[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Building a package needing the workdir of another package
In article <20090223220320.GC5522%orion.math.uni-bonn.de@localhost> Edgar wrote:
: What's the intended way of building a package that needs files from the
working directory of the build of another package?
Find another solution (like the ones you suggested below). While
this was done in the past, it is deemed unacceptable now. As just one
reason, a make clean in one package should not break the build of
: I'm trying to pkgsrc dovecot-managesieve. Building it needs files from a
built dovecot because it links against libraries dovecot doesn't export.
: Yes, best solution would be if dovecot did install those libraries, but I'm
not in a position to tell dovecot's or managesieve's authors that should be
: Solution 1: Use DISTFILES, CONFIGURE_DIRS and BUILD_DIRS to build dovecot (or
at least, the relevant libraries) inside dovecot-managesieve's working
directory. Should probably work, but duplicates both build time and pkgsrc
pkgsrc configuration could be shared via Makefile.common.
: Solution 2: Don't build managesieve as a separate package, but as an option
to the dovecot package. Should work too, but breaks modularity.
Solution 3: make our dovecot package install the needed libraries,
perhaps in a non-standard location (e.g. $LOCALBASE/lib/dovecot) so
they are not found unless explicitly looked for.
Main Index |
Thread Index |