Date: Thu, 1 Nov 2001 13:31:04 -0600 From: Alfred Perlstein <bright@mu.org> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: "Andrey A. Chernov" <ache@nagual.pp.ru>, David Wolfskill <david@catwhisker.org>, current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: buildworld breakage during "make depend" at usr.bin/kdump Message-ID: <20011101133104.H15052@elvis.mu.org> In-Reply-To: <91693.1004642592@axl.seasidesoftware.co.za>; from sheldonh@starjuice.net on Thu, Nov 01, 2001 at 09:23:12PM %2B0200 References: <20011101220836.A76061@nagual.pp.ru> <91693.1004642592@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
* Sheldon Hearn <sheldonh@starjuice.net> [011101 13:27] wrote:
>
>
> On Thu, 01 Nov 2001 22:08:36 +0300, "Andrey A. Chernov" wrote:
>
> > No, awk should be fixed instead to conform POSIX specs, or switched back
> > to gawk.
>
> It's not a binary decision. What we should probably do is:
>
> 1) Disconnect bwk-awk from the build.
>
> 2) Connect gawk to the build.
>
> 3) Fix bwk-awk and / or in-tree scripts that rely on gawkisms.
>
> 4) Disconnect gawk from the build.
>
> 5) Connect bwk-awk to the build.
>
> 6) Issue a fat HEADS UP to -current (and probably -ports).
Although I admit the fallout has been somewhat painful, let's
try to make do with it, if we disconnect the new awk I feel
that we will keep repeating this cycle, basically each activation
will see new problems requiring another disconnect. Let's just
get it fixed. :)
--
-Alfred Perlstein [alfred@freebsd.org]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
http://www.morons.org/rants/gpl-harmful.php3
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011101133104.H15052>