Date: Fri, 26 Apr 2002 16:20:17 -0700
From: Maxime Henrion <mux@freebsd.org>
To: ports@FreeBSD.org
Cc: Edwin Groothuis <edwin@mavetju.org>
Subject: Re: patch to have make clean not recurse in ${PORTSDIR}
Message-ID: <20020426232017.GC42922@elvis.mu.org>
In-Reply-To: <20020427090419.F56612@k7.mavetju.org>
References: <20020424224454.GM88736@elvis.mu.org> <20020424191430.W62277-100000@zoot.corp.yahoo.com> <20020426204935.GA42922@elvis.mu.org> <3CC9D357.9010105@owt.com> <20020426224107.GB42922@elvis.mu.org> <20020427090419.F56612@k7.mavetju.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Edwin Groothuis wrote: > On Fri, Apr 26, 2002 at 03:41:07PM -0700, Maxime Henrion wrote: > > Kent Stewart wrote: > > > I think that as long as a make will automatically install all of the > > > b-deps and r-deps of a port the default should be what it is. If you > > > do not clean what you have generated, people will have a shock from > > > all of the code that suddenly appeared and caught them off guard. > > > > This only affects a make clean in /usr/ports. Not the rest. So > > everything will still get cleaned. > > It should also affect the make clean in /usr/ports/*, if they are > not a port-directory. I disagree. Doing a "make clean" in /usr/ports with or without NOCLEANDEPENDS=yes has the same end result, it's just a lot faster with it, and also much more logical. This is not the case when in a ports category and people may not want "make clean" to not follow the dependencies in that case, so I'm not gonna change the default there. > The find /usr/ports -name Makefile is *not* a good solution, since > the design of the ports-layout is to modular and hierarchical[sp]. > There even might be ports (I agree, there are none) which require > a different behaviour on a "make clean" then a "rm -rf work". > > For example, if I make a port which remembers certain settings > before a compile (i.e. postfix, or ghostview-gnu) and the next time > the port is made I want to use the old settings (otherwise they > should have done a "make config"). > A "make clean" anywhere would rebuild the port with the old settings... > A "find /usr/ports -name work | xargs rm -rf" would destroy the settings. I'm not sure to understand what you are talking about here but it seems to me it's a different problem. Maxime 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?20020426232017.GC42922>