From owner-freebsd-ports Tue Sep 24 03:52:19 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA08357 for ports-outgoing; Tue, 24 Sep 1996 03:52:19 -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 DAA08314; Tue, 24 Sep 1996 03:52:07 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id MAA26394; Tue, 24 Sep 1996 12:30:51 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with SMTP id MAA01193; Tue, 24 Sep 1996 12:23:38 +0200 (MET DST) Date: Tue, 24 Sep 1996 12:23:38 +0200 (MET DST) From: Andreas Klemm To: Satoshi Asami cc: jkh@time.cdrom.com, andreas@freebsd.org, ports@freebsd.org Subject: Re: cvs commit: ports/graphics/xv Makefile In-Reply-To: <199609240859.BAA18585@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: > Well, I wouldn't call that a "bug" though. The problem here is that > we don't really know if the dependency was built just for this port or > not. > > For instance, if someone is trying to fix a bug in the jpeg port, and > a "make clean" in xv deletes jpeg's work directory with all his > patches and stuff, we'll have one very unhappy hacker. ;) But in *most* cases (99.8%) people are only 'customers', not ports hackers. They are only _using_ a port. That are the ones who wonder, why the /usr filesystem grows and grows after installing some ports ;) > I can change bsd.port.mk to keep the list of ports actually built > because of dependencies, but is this really worth it? The ports collection promises the customers an automated process to install a software simply via 'make all install clean'... Nobody told them that this is a semi automated process, where you have to go through the /usr/ports filesystems after building installing and cleaning a port and to do a 'make clean' here and there. It would be fine and useful to implement this in bsd.port.mk. What do the others think ?! 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 <<<