From owner-freebsd-ports Tue Sep 24 18:58:58 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA01802 for ports-outgoing; Tue, 24 Sep 1996 18:58:58 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA01747; Tue, 24 Sep 1996 18:58:47 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id DAA29381; Wed, 25 Sep 1996 03:45:40 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with SMTP id DAA01286; Wed, 25 Sep 1996 03:16:47 +0200 (MET DST) Date: Wed, 25 Sep 1996 03:16:47 +0200 (MET DST) From: Andreas Klemm To: Satoshi Asami cc: jkh@time.cdrom.com, ports@freebsd.org Subject: Re: cvs commit: ports/graphics/xv Makefile In-Reply-To: <199609241133.EAA00931@silvia.HIP.Berkeley.EDU> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Sep 1996, Satoshi Asami wrote: > * normally (and even if you're working on a custom port you should be > * doing it elsewhere than in /usr/ports), I'd say we should err on the > > Well, just to let you know, I always work in ${PORTSDIR} (so I can > easily cvs diff and stuff) when I'm fixing ports, and it has been > quite convenient. But I'll admit the chance of another port's "make > clean" blowing my port away is pretty slim.... But it doesn't protect you from situations, like: "Captain, I think we are too low on space for the new XFree86 build, so we have to do a ( cd /usr/ports; make clean) ...." And I think your special case is not the default for 99% of the FreeBSD users. What about the following idea ... you could do a local wrapper around that new make clean, that we discuss, to protect your work on your machine. Many users will be happy, that make clean does his job more thoroughly and you are on the save side... Or another idea ... I hear Satoshi arguing "but I don't want a non standard bsd.port.mk" ... and he is right... Couldn't we make a new environment variable for make in /etc/make.conf, so that people with similar interests like Satoshi could easily switch, if they like a thorough 'make clean' in /usr/ports or not ?! Compromise ;) Andreas /// andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<<