From owner-freebsd-arch Sun Oct 17 11:59:19 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 4F39514E57 for ; Sun, 17 Oct 1999 11:59:16 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id UAA03716 for ; Sun, 17 Oct 1999 20:59:15 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA69192 for freebsd-arch@freebsd.org; Sun, 17 Oct 1999 20:59:14 +0200 (MET DST) Received: from dt050n71.san.rr.com (dt050n71.san.rr.com [204.210.31.113]) by hub.freebsd.org (Postfix) with ESMTP id 8225C14E57 for ; Sun, 17 Oct 1999 11:59:07 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt050n71.san.rr.com (8.9.3/8.8.8) with ESMTP id LAA09781; Sun, 17 Oct 1999 11:58:48 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <380A1C68.BF17ED9F@gorean.org> Date: Sun, 17 Oct 1999 11:58:48 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT-0927 i386) X-Accept-Language: en MIME-Version: 1.0 To: Marcel Moolenaar Cc: arch@freebsd.org Subject: Re: make world issues References: <3808BC30.2699465B@scc.nl>, <199910162136.PAA01266@harmony.village.org> <38099CCB.99EE1C97@scc.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel Moolenaar wrote: > > [taken of -arch] > > Warner Losh wrote: > > > Personally, I would have included backward compatibiltiy shims in libc > > for the signal stuff for a while, but that appears to have been hard > > to do... > > The problem I have with such a workaround (in general) is that it is > difficult (in general) to know when you can remove the shims. The simple solution for that problem was already suggested by someone else, but may have been lost in the noise. You require a define to incorporate the shims. Make the define a stock part of the "make upgrade," or whatever we want to call it from 2.2.x/3.x to 4.x, and put it in UPDATING so that -current -> later -current upgraders can also use it. While they're there they're harmless, and/or necessary, and once your system is all upgraded they go away on the next kernel rebuild. With proper comments in the code as to what they are there for, and a recommended time of nuking (say, one year after 4.0-Release) all of the admittedly possible scenarios you mention vanish. I've done exactly this on some other projects I've worked on and never had a problem with it. Doug -- "Stop it, I'm gettin' misty." - Mel Gibson as Porter, "Payback" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message