Date: Mon, 16 Nov 2009 15:58:23 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Sandra Kachelmann <s.kachelmann@googlemail.com> Cc: ports@freebsd.org Subject: Re: remove BUILD_DEPENDS automatically after install Message-ID: <4B01E71F.5050909@FreeBSD.org> In-Reply-To: <91b92520911160312q62c777absb735c44334328f05@mail.gmail.com> References: <91b92520911151444k742351bfl9ae20fb82a604bd5@mail.gmail.com> <20091116000643.GA14996@owl.midgard.homeip.net> <91b92520911160312q62c777absb735c44334328f05@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sandra Kachelmann wrote: > (portmaster author cc:ed) > > On Mon, Nov 16, 2009 at 1:06 AM, Erik Trulsson <ertr1013@student.uu.se> wrote: >> On Sun, Nov 15, 2009 at 11:44:04PM +0100, Sandra Kachelmann wrote: >>> Is there a reason why BUILD_DEPENDS aren't being removed after a port >>> has been installed and if no other installed port depends on it? >> How do you know that the user does not want that port installed? >> And what if the user will install 20 other ports afterwards - all of which >> is that same port as a BUILD_DEPENDS - should that port be >> installed/deinstalled each and every time? > > It would be nice if this was configurable. Maybe it could be even > integrated into portupgrade or portmaster. If such a port is installed > directly it could get a package entry DIRECT_INSTALLED=yes in > /var/db/pkg/.. or something (there is probably a better way to do > this). I have a new feature in the svn version of portmaster called --packages-build that for any given run creates an internal list of dependencies that are only ever listed as build deps (never run deps) and installs packages for them but builds everything else. This feature was created at the request of one of companies that sponsored the package installation code. Currently it does not pkg_delete those packages when it's done, but I could easily add that. Actually I suppose it would not be too hard to extend that "list of build only deps" idea to a general feature which deletes them when done. Something like --delete-build-only maybe? This would be limited to the subset of the list of build-only deps that portmaster actually installed. Just because something is build-only for a given run of portmaster doesn't mean that it isn't a run dep for something else if it is already installed. >> (Personally I would be *very* annoyed if, for example, libtool or >> automake/autoconf would be reinstalled every time I installed a port which >> had one of them as a build-time dependency. Well then don't use the option. :) Options are generally good things. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B01E71F.5050909>