Date: Thu, 01 Aug 2013 11:25:17 -0500 From: Stephen Montgomery-Smith <stephen@missouri.edu> To: Chris H <bsd-lists@1command.com> Cc: freebsd-stable <freebsd-stable@freebsd.org>, freebsd-perl <freebsd-perl@freebsd.org> Subject: Re: Please remove Perl from ports Message-ID: <51FA8BED.3060103@missouri.edu> In-Reply-To: <622977670ec4e80b844c5c6c978ae6f6.authenticated@ultimatedns.net> References: <622977670ec4e80b844c5c6c978ae6f6.authenticated@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/01/2013 10:31 AM, Chris H wrote:
> So, in the end; why did Perl have to be relocated? Is my only
> recourse at this point to
> # cd /
> # rm -rf .
When I get into this kind of bad situation, I usually do something
slightly less drastic:
# pkg_delete -a
# find -d /usr/local -type d -exec rmdir {} \;
This last command removes empty directories in /usr/local (it also
produces lots of error messages when it tries to remove non-empty
directories). Then I look through the contents of /usr/local,
especially if there is anything in /usr/local/etc or /usr/local/libexec
where some of my manually changed configuration files reside. And then
I delete any crud left over that I know I don't need.
After that, I rebuild all the ports from scratch.
Finally, I do understand why you feel the need to vent, and I don't want
to belittle your feelings of frustration. But I do think everyone is
trying their best. I like to tell people that running FreeBSD or Linux
is like owning a souped up sports car - usually it runs really well, but
it often needs a lot of attention. (Windows is like driving a cheap car
that breaks down all the time, but engine is designed in such a way as
to be totally inaccessible with regards to repairs. And Apple is like
driving a BMW - it mostly works well but you pay a lot for it.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51FA8BED.3060103>