remove BUILD_DEPENDS automatically after install

[Sandra Kachelmann]

On Tue, Nov 17, 2009 at 12:58 AM, Doug Barton <dougb at freebsd.org> wrote:
> Sandra Kachelmann wrote:
>> (portmaster author cc:ed)
>>
>> On Mon, Nov 16, 2009 at 1:06 AM, Erik Trulsson <ertr1013 at 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.

This is exactly what I was looking for.

> 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

I would find such an option extremely useful.

> 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.

Or if it's already installed before the actual port build it could be
considered as "wanted" and therefor not to be deleted after the build.

Just out of curiosity, is your svn repository publicly accessible?

Thank you so much for the good work.

Sandra