On Nov 19, 2011, at 12:08 PM, Ryan Schmidt wrote:
> Hope you don't mind, I'm replying on the mailing list.
Of course not. :-)
>> Concerning #31186 I just wanted to say that, yes, you are right that the
>> Guide isn't wrong, BUT, it would be less confusing if the "/MacPorts"
>> subfolder would not be omitted. The prefix certainly already ensures the
>> distinguishing between different installs, but the "/MacPorts" subfolder
>> would also keep the parallel installs in the same directory tree scheme.
>
> I don't see a reason to suggest doing that. Feel free to do it yourself in
> your own installation if that makes you feel more organized. To me it's
> redundant.
+1
> I'd much rather make the default applications_dir ${prefix}/Applications,
> with a symlink at /Applications/MacPorts pointing to it, since the #1 reason
> people change applications_dir is to avoid overlap between multiple MacPorts
> installations. At least I assume that's the main reason. It's certainly the
> reason I do. We already changed the default frameworks_dir from
> /Library/Frameworks to ${prefix}/Library/Frameworks some years ago for the
> same reason. I'm just not sure how we're going to handle upgrading people
> from the old applications_dir default to the new one.
OK, so I won't change anything in the Guide. Thanks for your feedback.
> Yes, our documentation situation is not very cohesive.
+1
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
