Date: Fri, 10 Feb 2006 14:28:28 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: ports@freebsd.org Subject: Re: requirements for bsd.xxx.mk file Message-ID: <20060210142828.ynjvl9uu4ggogkkk@netchild.homeip.net> In-Reply-To: <20060210022408.GA21255@odin.ac.hmc.edu> References: <20060210022408.GA21255@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis <brooks@one-eyed-alien.net> wrote:
> 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
I think you need more than 2... :-)
We have no rules here. So if you think for yourself the number of ports
reached the critical mass, just go ahead.
> ${PORTSDIR}/www/drupal/Makefile.common instead like PEAR does?
IMHO the Makefile.common approach is a nice way to prototype/develop a first
working initial version. While a bsd.xxx.mk file is the "ok, we have
something to base our effort on, let's make it official" approach.
Bye,
Alexander.
--
http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
I couldn't very well chop your hand off and bring it to the store,
could I?
-- Homer Simpson
Life on the Fast Lane
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060210142828.ynjvl9uu4ggogkkk>