From owner-freebsd-hackers Wed Feb 5 11:26:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA03976 for hackers-outgoing; Wed, 5 Feb 1997 11:26:20 -0800 (PST) Received: from relay.nuxi.com (nuxi.ucdavis.edu [128.120.37.176]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03969; Wed, 5 Feb 1997 11:26:14 -0800 (PST) Received: from dragon.nuxi.com (reqf-022.ucdavis.edu [128.120.253.142]) by relay.nuxi.com (8.8.4/8.6.12) with ESMTP id LAA25462; Wed, 5 Feb 1997 11:26:16 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.8.4/8.7.3) id LAA07202; Wed, 5 Feb 1997 11:26:04 -0800 (PST) Message-ID: <19970205112604.AI13761@dragon.nuxi.com> Date: Wed, 5 Feb 1997 11:26:04 -0800 From: obrien@NUXI.com (David O'Brien) To: chuckr@glue.umd.edu (Chuck Robey) Cc: freebsd-ports@freebsd.org (FreeBSD ports list), hackers@freebsd.org Subject: Re: conditionally including References: <19970205003343.YB13323@dragon.nuxi.com> X-Mailer: Mutt 0.59-PL19 Mime-Version: 1.0 Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 In-Reply-To: ; from Chuck Robey on Feb 5, 1997 08:17:18 -0500 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chuck Robey writes: > On Wed, 5 Feb 1997, David O'Brien wrote: > > David, I don't understand why you don't want to use __FreeBSD__, > __NetBSD__, and __OpenBSD__ for non-kernel stuff. > The __44bsd__ thing doesn't exist, and if you start it, 75% of FreeBSD > folks and ALL of everyone else in NetBSD and OpenBSD will be out in the > cold. True. But I would only go down this route with the assurance from the other camps that they would do the same. When I started this I was with them all at USENIX and I had easy access to convence them this is a Good Thing. Since both NetBSD and OpenBSD pretty much use our ports (and I think they like not having to throw resources on them), it would be in their best interests for the return they get. > I probably misunderstand part, but what functionality will be gained from > adding __44bsd__? I want to note that the approach I'm pushing works now > for Xfree86 just fine. (note for others, Chuck's approach is use __FreeBSD__, __NetBSD__, and __OpenBSD__) Your approach is fine. I'm just trying to follow the guidence of the handbook. I'm thinking of ripping out the verbage on not using these macros. They seem to be the only true way of dealing with this. If anyone knows who wrote those words, I'd love to start a dialog with them. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org)