Date: Thu, 16 Mar 2000 13:03:41 -0800 (PST) From: Kris Kennaway <kris@FreeBSD.org> To: Matthew Lariz <lariz@best.net> Cc: ports@freebsd.org Subject: Re: Make files.. (fwd) Message-ID: <Pine.BSF.4.21.0003161301010.81682-100000@freefall.freebsd.org> In-Reply-To: <Pine.BSF.4.21.0003161255310.7671-100000@flea.best.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Mar 2000, Matthew Lariz wrote:
> Now here's my question. If most of the ports are indifferent to the
> system version, and the bsd.ports.mk file is applied globally, wouldn't it
> make more practical sense to put it in the make files for the individual
> ports?
This is the route OpenBSD (and I believe NetBSD) have gone - they have
something like a REQUIRE_VERSION which holds the $FreeBSD$ tag of
bsd.port.mk the port requires to build. Of course theres the
chicken-and-egg problem of having to have a bsd.port.mk new enough to
understand what REQUIRE_VERSION actually means, but thats a once-off and
could be handled by our existing "too old" mechanism to force users to
upgrade to the new one.
With a bit of work we could probably go that way as well.
Kris
P.S. Installing the FreeBSD upgrade kit from www.freebsd.org/ports would
solve your problem of "too old a system".
----
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" 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.21.0003161301010.81682-100000>