Date: Thu, 1 Apr 1999 06:52:35 -0600 (CST) From: Richard Wackerbarth <rkw@dataplex.net> To: Satoshi - the Wraith - Asami <asami@FreeBSD.ORG> Cc: jkh@zippy.cdrom.com, jhay@mikom.csir.co.za, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion Message-ID: <Pine.BSF.4.05.9904010627530.3305-100000@nomad.dataplex.net> In-Reply-To: <199904011036.CAA52719@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
I have to agree that the problem is real. However, let me point out that a "one identifier" solution is very short sided. There are two distinct environments to be considered. The HOST environment and the TARGET environment. For convience, we should also consider a TOOLSET environment which is a cross between the two. Just as it is "wrong" to use compiler variables like, "__FreeBSD__" to control target compilations (except as a default), it is also "wrong" to do so for the ports. The group has come around to the idea that the files in /usr/include represent the HOST and not the TARGET. I suggest that you dig out my old proposal for tagging the HOST in /usr/include. The natural tag for the TARGET would be in /usr/src/include. However, I can see some problems with this for the ports tree. The more general mechanism allows us to "register" capabilities. (Shades of some commercial OS'es) However, we may not want to do things in such a unified manner :-) On Thu, 1 Apr 1999, Satoshi - the Wraith - Asami wrote: > It has been pointed out many times in the past > that we need something to ensure bsd.port.mk can synchronize itself > with the rest of the system > > The question is, can I ask you to make sysinstall write some kind of > version info that can be used by bsd.port.mk to identify the age of > the system? > > The problem is real, we've been bitten too many times in the past > (haven't you seen all the "where's fetch -A?" and other more subtle > breakages that are caused by ports and system mismatch) 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?Pine.BSF.4.05.9904010627530.3305-100000>