Date: Tue, 22 Nov 2005 05:15:09 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Nate Eldredge <nge@cs.hmc.edu> Cc: freebsd-current@freebsd.org Subject: Re: [patch] remove build dependencies in bsd.ports.mk Message-ID: <20051121181509.GB4267@cirb503493.alcatel.com.au> In-Reply-To: <Pine.GSO.4.63.0511210146040.20520@turing> References: <200511201403.58634.nb_root@videotron.ca> <20051120190852.GB2963@soaustin.net> <20051121090813.GD21670@uk.tiscali.com> <Pine.GSO.4.63.0511210146040.20520@turing>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2005-Nov-21 01:53:13 -0800, Nate Eldredge wrote: >works as follows. Suppose package Foo requires package Bar, and neither >is currently installed. When you request the installation of Foo, Bar is >also installed, but an "auto" flag is set for Bar. Any package with the >auto flag set is only kept so long as something depends on it. If I >remove Foo, Bar is automatically removed as well, provided I haven't in >the meantime added anything else which depends on it. This would work OK for runtime dependencies but handling build-time only dependencies would need some careful thought. Whilst it might be reasonable to automatically remove gcc-ooo after installing Openoffice.org, I probably wouldn't want autoconf, automake, imake etc deleted immediately after building something that needed them. >I would guess build dependencies should be treated like regular >dependencies. If they're removed after building, then you would have to >reinstall them every time you upgrade the depending package. They can't be treated totally as runtime dependencies because you don't need (or want) them installed if you install a package (rather than building a port). >Anyway, AFAIK FreeBSD doesn't have anything like this, but it would be >nifty if it did. Agreed. -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051121181509.GB4267>