Date: Sat, 19 Jun 1999 15:11:51 -0700 From: Chris Piazza <cpiazza@home.net> To: Alfred Perlstein <bright@rush.net> Cc: ports@FreeBSD.ORG Subject: Re: where are the README.html files in ports when cvs? Message-ID: <19990619151151.A381@norn.ca.eu.org> In-Reply-To: <Pine.BSF.3.96.990619161127.14320S-100000@cygnus.rush.net>; from Alfred Perlstein on Sat, Jun 19, 1999 at 04:16:20PM -0500 References: <Pine.BSF.3.96.990619161127.14320S-100000@cygnus.rush.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 19, 1999 at 04:16:20PM -0500, Alfred Perlstein wrote: > > How come after doing an install of the ports collection during a fresh > install I get those nifty (and mighty handy) README.html files > in the directories, but I don't get them when I use CVSup to grab > ports? I personally delete them after I fresh install a system but here is how you make them: You can create them with a `make readmes' in the port directory. a `make readme' in a single port directory creates it for that, port too. > > One more thing, why don't we enable passing the makes a flag > to specify how many makes we would like to have concurrant, something > like NBUILDJOBS=n to pass make a -jn flag. Ports could be > marked for parralell builds via a define... that way dependancies > that aren't -j safe won't be compiled that way... MAKE_ARGS="-j 8" make all will do what you want, save the flag to not use parallel builds if the port doesn't support it. -Chris -- cpiazza@home.net cpiazza@FreeBSD.ORG FreeBSD: The power to serve! http://www.FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990619151151.A381>