Date: Thu, 9 Feb 2006 18:24:08 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: ports@freebsd.org Subject: requirements for bsd.xxx.mk file Message-ID: <20060210022408.GA21255@odin.ac.hmc.edu>
next in thread | raw e-mail | index | archive | help
--k+w/mQv8wyuph6w0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
I've been doing a deployment of drupal at work and I've ported a couple
modules with plans to port more. I've built up a framework to make
individual modules easy to port, but at the moment it's in the form of a
Makefile and a pkg-install.in script that are mostly duplicated. I'm
wondering what the bar is for creating a bsd.xxx.mk. How many ports are
needed to justify the overhead? Should I use a
${PORTSDIR}/www/drupal/Makefile.common instead like PEAR does?
-- Brooks
--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
--k+w/mQv8wyuph6w0
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFD6/lHXY6L6fI4GtQRAv0qAJ4oecBoQg/xeb9RC5y9KF4YT20wxgCgiLSX
cElztDFwVTw7P8q0o73O8h8=
=LVOk
-----END PGP SIGNATURE-----
--k+w/mQv8wyuph6w0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060210022408.GA21255>