/usr/local question

[Bradley Giesbrecht]

On Apr 4, 2012, at 3:39 PM, Jan Stary wrote:

>>> No it didn't magically ended up there. You installed it there.
>>> And you were told before you installed it there that it will
>>> end up there.
>> 
>> I didn't say that, I said *magically*.
>> Of course I know there was no magic involved. Phew...
> 
> Jesus, I am not implying you think it was magic.
> I am just pointing out that you installed it there yourself,
> and if it broke things, that's not a failure of the packaging system.
> 
>> Of course MacPorts WILL install libpng in /opt/local.
>> But when the port that requires libpng is then built the compiler may chose
>> the libpng that got installed in /usr/local.
> 
> Yes. And if /usr/local was where macports installs its stuff,
> then this would mean that the compiler picked up what macports
> installed, by default.

When MacPorts is prefixed in /opt/local and some process installs files to /usr/local it is easy to move /usr/local out of the way to solve MacPorts installation issues. If MacPorts is prefixed in /usr/local this would be impossible.


Regards,
Bradley Giesbrecht (pixilla)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2763 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20120404/3ebc7f97/attachment.bin>