Date: Sun, 18 Jan 1998 20:26:49 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Warner Losh <imp@village.org> Cc: John Fieber <jfieber@indiana.edu>, ports@FreeBSD.ORG Subject: Re: Docs for bsd.ports.mk Message-ID: <3284.885184009@time.cdrom.com> In-Reply-To: Your message of "Sun, 18 Jan 1998 21:03:16 MST." <199801190403.VAA02286@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Perhaps the best solution is to revamp the web docs until they're a bit less confusingly organized and also cover more of the details. Then write a man page which tries to give the ports collection in overview and simply refers to various URLs for the "meaty" stuff. Then you'd only really have the web pages to maintain as the ports collection evolved and the man page would stay largely change-proof. Jordan > In message <Pine.BSF.3.96.980118223014.26398Q-100000@fallout.campusview.india na.edu> John Fieber writes: > : You mean beyond what www.freebsd.org/handbook/porting.html > : provides? > > Yes. Right now the porting.html talks about writing a port. It is > excellent for writing a port. However, there are many dirty tricks > that have been used for building ports. The NOCLEANDEPENDS question I > just had, for example. Also things like PREFIX and alternative > FETCH_CMDs and the like would be good to have as well. > > Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3284.885184009>