Date: Thu, 12 Sep 1996 02:26:28 -0700 (PDT) From: "David E. O'Brien" <obrien@Nuxi.cs.ucdavis.edu> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: obrien@Nuxi.cs.ucdavis.edu, gurney_j@resnet.uoregon.edu, freebsd-ports@freefall.freebsd.org Subject: Re: port of su2 Message-ID: <199609120926.CAA03973@relay.nuxi.com> In-Reply-To: <2781.842518438@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 12, 96 01:53:58 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > suggest you get almost any existing port and follow its example. Also, > > take a glance at /usr/share/mk/bsd.port.mk. It is *very* readable as > > makefiles go. > > I've read this 3 times and still can't figure out if it's very thinly > veiled sarcasm or not. :-) No sarcasm at all. It has *tons* of clear readable comments. I wish every complex Makefile I've ever had to read was this well laid out and commented. There is no need for special documentation of the predefined symbols, because they are so easy to find (along with their intended use). bsd.port.mk is a model for other complext development projects to follow. The "as makefiles go" means, yes, you still have to know some basic Makefile syntax to understand what it is doing -- but not really that much (especially since there aren't any implicit targets and things like $*,$<, etc used). -- David (obrien@nuxi.com)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609120926.CAA03973>