From owner-freebsd-current Wed Nov 18 04:42:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29518 for freebsd-current-outgoing; Wed, 18 Nov 1998 04:42:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29512 for ; Wed, 18 Nov 1998 04:42:33 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id XAA29115; Wed, 18 Nov 1998 23:12:05 +1030 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA00202; Wed, 18 Nov 1998 23:12:03 +1030 Date: Wed, 18 Nov 1998 23:12:01 +1030 (CST) From: Kris Kennaway To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Richard Wackerbarth wrote: > > Eivind Eklund wrote: > > > I think the first one also is nice to have. Some of us want to update perl > > > and the rest of the system independently of each other (e.g, due to local > > > hacks to the perl code, for people doing development of Perl itself). > > > > OK - I'll buy that. I'd prefer it to be undocumented, so people won't find > > the switch, frob it, and get burnt. > > BUZZ ... WRONG ANSWER. > > Please document it properly so that people won't get burned. It's better > to tell someone why they shouldn't play with matches rather than just > hiding them on the top shelf. :-) Setting NOPERL=true is useful to me because it takes a fair mount of time to rebuild, even if the source hasn't changed. I recompile my world using 'make depend;make all', which while it's not the recommended or supported way to recompile things, does save lots of compilation time (I haven't needed to do a make world since E-day). Leaving PERL building turned on causes lots of 'null' recompilation of things which haven't changed (formatting manpages, etc)..so I only bother to recompile it when I see a commit message stating something important has been changed. As long as the effects of setting the flag are documented, I don't see a problem with keeping it visible to casual inspection (as opposed to burying it somewhere where it will never be noticed :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message