requirements for bsd.xxx.mk file

[Brooks Davis]

On Fri, Feb 10, 2006 at 02:28:28PM +0100, Alexander Leidinger wrote:
> Brooks Davis <brooks at 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... :-)

I figured. :-)

> 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.

Sounds good, I'll start with that.

-- Brooks

-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20060210/1e86a7aa/attachment.bin