From owner-freebsd-current Tue Jun 4 8: 5:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from phnxpop6.phnx.uswest.net (phnxpop6.phnx.uswest.net [206.80.192.6]) by hub.freebsd.org (Postfix) with SMTP id DE2D237B411 for ; Tue, 4 Jun 2002 08:05:20 -0700 (PDT) Received: (qmail 44590 invoked by uid 0); 4 Jun 2002 15:05:29 -0000 Received: from zdialup172.phnx.uswest.net (HELO broken) (209.181.132.172) by phnxpop6.phnx.uswest.net with SMTP; 4 Jun 2002 15:05:29 -0000 Date: Tue, 4 Jun 2002 08:05:31 -0700 Message-ID: <004e01c20bd9$46077da0$0a00a8c0@broken> From: "Dan Trainor" To: current@FreeBSD.ORG Subject: RE: State of the ports collection MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20020604134220.B42142@treetop.robbins.dropbear.id.au> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What's going to happen to all these ports that still depend on file locations in the 4.5 release(s)? The reason I ask is that I see that now we're going to have to make two kinds of ports - one for 4.x and one for 5.x, or are header files and stuff like that stored as global variables... or something. Kris Kennaway talked a bit about moving specific headers (and possibly more) to different locations: :: * (>27 ports) The header was moved, breaking :: * (>35 ports) Something caused sys_nerr to change prototypes. It looks like this might be because the definition of __const from has changed, but I can't see why. See for example I don't know, it was just something that concerned me. I'd hate to see version-specific ports, and I'm hoping it doesn't come down to that. - dt - dan@ript.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message