Date: Wed, 3 Feb 1999 12:49:21 -0800 (PST) From: brooks@one-eyed-alien.net To: Archie Cobbs <archie@whistle.com> Cc: "Steve O'Hara-Smith" <steveo@iol.ie>, rbezuide@oskar.nanoteq.co.za, freebsd-current@FreeBSD.ORG Subject: Re: make port and bsd.port.mk Message-ID: <Pine.GSO.4.05.9902031244530.19927-100000@orion.ac.hmc.edu> In-Reply-To: <199902032031.MAA25882@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Feb 1999, Archie Cobbs wrote: > Steve O'Hara-Smith writes: > > > There is no /usr/ports/Mk directory on my machine > > > Where can I find these files or is it a bug ?? > > > > cvsup your ports and all will be well. > > I'm curious what the reason for moving the includes to /usr/ports/Mk > was.. is this to insure better consistency? That would make sense. It makes since to me, but I'm a little confused about the timing of this change. It was rather annoying to update my 2.2.8-STABLE machine a day or two after being told that cvsuping ports on a 2.2 machine might cause breakage (re: the no more 2.2 support announcement) to find that *not* cvsuping ports broke my ports collection because the makefiles moved to /usr/ports/Mk. Don't get me wrong, I like the change, but the timing seems less the perfect. -- Brooks 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.GSO.4.05.9902031244530.19927-100000>