From owner-freebsd-current Wed Feb 3 12:50:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20099 for freebsd-current-outgoing; Wed, 3 Feb 1999 12:50:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20070 for ; Wed, 3 Feb 1999 12:50:14 -0800 (PST) (envelope-from brooks@one-eyed-alien.net) From: brooks@one-eyed-alien.net Received: from localhost (brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id MAA27018; Wed, 3 Feb 1999 12:49:21 -0800 (PST) X-Authentication-Warning: orion.ac.hmc.edu: brdavis owned process doing -bs Date: Wed, 3 Feb 1999 12:49:21 -0800 (PST) X-Sender: brdavis@orion.ac.hmc.edu To: Archie Cobbs cc: "Steve O'Hara-Smith" , rbezuide@oskar.nanoteq.co.za, freebsd-current@FreeBSD.ORG Subject: Re: make port and bsd.port.mk In-Reply-To: <199902032031.MAA25882@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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