Date: Tue, 23 Jan 2001 01:33:11 +0000 From: Brian Somers <brian@Awfulhak.org> To: Peter Wemm <peter@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, brian@Awfulhak.org Subject: Re: cvs commit: src Makefile.inc1 Message-ID: <200101230133.f0N1XB107675@hak.lan.Awfulhak.org> In-Reply-To: Message from Peter Wemm <peter@FreeBSD.org> of "Sun, 21 Jan 2001 23:29:49 PST." <200101220729.f0M7TnZ86477@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> peter 2001/01/21 23:29:49 PST
>
> Modified files:
> . Makefile.inc1
> Log:
> Using "KERNEL" for buildkernel was a very very bad mistake. $KERNEL is
> already used by the kernel makefiles themselves, and this leads to a lot
> of trouble when people put "KERNEL=MYKERNEL" in make.conf. Bite the bullet
> and change it to KERNCONF instead, before it gets too far entrenched.
>
> The kernel Makefiles use ${KERNEL} as the name of what to install the
> kernel as, eg: /boot/${KERNEL}/kernel or /${KERNEL}. This leads to much
> unhappiness with things like /LOCAL instead of /kernel. buildkernel is
> severely limited as it is only useful directly after a buildworld.
>
> Reviewed by: jhb
>
> Revision Changes Path
> 1.183 +5 -5 src/Makefile.inc1
I've had KERNEL= in /etc/make.conf for several months and on lots of
machines. It leads to no trouble that I can see with buildkernel/
installkernel.
Doing this may be broken for the old config, cd /blah/blah/compile/blah,
make method, so why not fix that rather than breaking everyone's
current configuration ?
Assuming you've got a good argument for breaking things, a HEADS UP
is probably in order.
--
Brian <brian@Awfulhak.org> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org>; <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101230133.f0N1XB107675>