<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Feb 28, 2014 at 8:44 AM, Jason Swails <span dir="ltr"><<a href="mailto:jason.swails@gmail.com" target="_blank">jason.swails@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">sudo port -f select --set postgresql postgresql93<br></div>
<br>
In my opinion, such protection is a Good Thing (TM). There's a way to<br>
work around it if you know the reason behind the file collision, but I<br>
certainly wouldn't want a program (especially one I run as root) to go<br>
around clobbering existing files without me knowing it.<br></blockquote></div><div class="gmail_extra"><br></div>Except the implication of their preamble is that that file was left around by removing the postgres92 port, because port select isn't sufficiently integrated and isn't cleared when a `select`ed port is removed.<br clear="all">
<div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>