Date: Thu, 15 Apr 2021 17:02:40 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Cleaning Ports Tree Message-ID: <d75ed69f-1f45-a54d-a979-ec12e8233f3c@tundraware.com> In-Reply-To: <ece5e434-1bc1-987f-7198-932822af2f40@heuristicsystems.com.au> References: <0a04f310-af5c-371c-0940-1b0af0f5aca4@tundraware.com> <ece5e434-1bc1-987f-7198-932822af2f40@heuristicsystems.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/15/21 4:05 PM, Dewayne Geraghty wrote:
> On 16/04/2021 6:37 am, Tim Daneliuk via freebsd-questions wrote:
>> I am aware that one can do this to clean the ports tree:
>>
>> cd /usr/ports
>> make clean
>>
>> However, this is very slow. Is there any reason not to do this instead:
>>
>> find /usr/ports -type d -name work -exec -vrf {} \;
>>
>> This second approach is much, much (much) faster, I just want to make
>> sure I am not creating nasty side-effects thereby.
>>
> I've done a similar thing since 2003 without ill effects. For
> completeness I also have (in make.conf):
>
> WRKDIRPREFIX=/var/ports # when I perform a rebuild, I simply delete the
> subdirs
> DISTDIR=/distfiles # so all the distfiles are in one place
> PACKAGES=/packages # same for the outputs.
>
> It also allows the use of multiple devices.
This is actually even cleaner. A simple rm -rf /var/ports cleanses the system ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d75ed69f-1f45-a54d-a979-ec12e8233f3c>