Re: RFD/CFT: www/angie: use upstream versions for all modules; using intermediate variables for DISTVERSION/PORTREVISION?

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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEErQouifc5ybqTEVgvLx1vPG8zTyoFAmjyOz8ACgkQLx1vPG8z
Tyq9OQf/YM/xCGYRfzU7JqKGnlI8h/P/vJcbBCnDg9nHk4AyKXiMhl1ahmW7tLIr
3PNI6r+RYffzSkJ+1GhQ+pBdnYgSacnxqyKbgbNqjJgrexJUHCkZ5RAHanL29mIJ
MEnGhM0OIM8K96cUzHdFrFG4Z766QDKGN13vDkFvAFB1tMgdfuXPmiV++83xiVB1
XKr5SvU+9gaaogjyOWl8Cd7ovrEh516YvpZn1VQnI7t4j8OB289qb/D13hZLFQ2T
6rFdNQrZw00NCHW+HN+Dd9i/ZfGtXVGZuVDD/gk/E4N2d2nRYMifIy//y1jdspF1
bsVYv4Vsb2Poy81MeRQpRoBfWTX4XQ==
=SaTw
-----END PGP SIGNATURE-----