Hi Robert, > One pattern that I like to use is to build a framework Makefile in the > master port that is included by the slave port. See e.g. devel/schilybase > and its dependent ports. This allows you to sidestep the whole issue of > the slave port getting the whole master port makefile. Do disregard the > warnings of portlint on the master port file having an uncommon name.
That's indeed an elegant solution to provide a separate Makefile for all slaves within the master port. I'll definitely have a look at this. I'd still need a way to have both version numbers (slave and master) present during module build; but this way I can just use a custom variable in that slave-Makefile, allowing the www/angie Makefile and all slave Makefiles to use DISTVERSION as intended. (Or is there some mechanism to dynamically get another port's current version from a Makefile?) Thanks, Sebastian -- Sebastian Oswald GnuPG-Key-ID: 0x313F3181
pgpYBuv17lBIq.pgp
Description: OpenPGP digital signature
