That's because the make clean in /usr/ports follows the dependencies which
makes it clean a lot of ports several times...
What you can try is to do a make -DNOCLEANDEPENDS clean.
Regards,
Maxime Henrion
David Kelly wrote:
> I'm sure to be off my rocker to suggest something like this 2 days
> before -RELEASE, but sometimes I don't clean up after installing a port
> and out of laziness simply do "make clean" from the /usr/ports/
> directory. Takes forever. And got to thinking about alternatives.
>
> # find /usr/ports -type d -name work -print -execdir make clean \; -prune
>
> is much faster than "make clean" from the top. It seems to work OK if a
> clean target is put in /usr/ports/Makefile just prior to the .include
> <bsd.port.subdir.mk>
>
> --
> David Kelly N4HHE, [EMAIL PROTECTED]
> =====================================================================
> The human mind ordinarily operates at only ten percent of its
> capacity -- the rest is overhead for the operating system.
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
--
Don't be fooled by cheap finnish imitations ; BSD is the One True Code
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
