<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote type="cite" class="">One thing that I've learned (thanks to people like Ryan and you etc) is to *never* touch MacPorts unless you are aware of the consequences. It's not that it's fragile -- far from it -- it's just that there are few user-serviceable parts inside.<br class=""></blockquote><br class=""><div class="">Well, thats the point: the conf files *are* the user-serviceable parts by definition. But the consequence of changing those parameters are not explicitly mentioned anywhere I'm aware of - certainly not in <a href="https://trac.macports.org/wiki/FAQ" class="">https://trac.macports.org/wiki/FAQ</a> or in macports.conf, where they are set:</div><div class=""><br class=""></div><div class=""><div class=""></div><blockquote type="cite" class=""><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class=""># Directory under which MacPorts should install ports. This must be</span></font></div><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class=""># where MacPorts itself is installed.</span></font></div><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class="">prefix /opt/local</span></font></div><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class=""><br class=""></span></font></div><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class=""># Directory for application bundles installed by ports.</span></font></div><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class="">applications_dir /Applications</span></font></div><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class=""><br class=""></span></font></div><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class=""># Directory for frameworks installed by ports.</span></font></div><div class=""><font color="#5856d6" face="Courier" class=""><span style="caret-color: rgb(88, 86, 214);" class="">frameworks_dir /opt/local/Library/Frameworks</span></font></div></blockquote><br class=""></div><div class="">I'll file a ticket to add this to the comments in macports.conf and the FAQ, or maybe even send a pull request.</div><div class=""><br class=""></div><div class="">Which leaves the question: can it be fixed and make archives work with customized locations, at least for "applications_dir"? Probably rather a question for the dev mailing list…</div></body></html>