<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On 17 Jan 2020, at 10:36 pm, Dave Allured - NOAA Affiliate via macports-users <<a href="mailto:macports-users@lists.macports.org" class="">macports-users@lists.macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Chris, thanks for the quick reply. You are correct, a private macports installation would enable testing ports without special privilege. Actually I have already done this many times for testing and debugging other cases.</div><div class=""><br class=""></div><div class="">However, I would like to find an intermediate solution that avoids full build-up from sources. My main reasons are (1) test sensitivity to installed ports in the system prefix; (2) save time and effort; and (3) be able to provide compact, uncomplicated reproducers to third parties.</div><div class=""><br class=""></div><div class="">If not currently possible, it would be nice to have a new feature to enable local repository testing, with fallback to the system prefix for everything not found in the local repository.</div></div></div></blockquote><div><br class=""></div>What you are asking for is I am afraid really not possible, I suspect. The installation prefix is a fundamental parameter in most port builds. Many directly use this via the ${prefix} variable, which is a single valued path. What you are asking for is for a port use to use one location for some ports and a second one from others. I just don’t see how that could work.</div><div><br class=""></div><div>I think your only option is really to go with a second installation using a custom prefix.</div><div><br class=""></div><div>Chris</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 17, 2020 at 3:09 PM Christopher Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" class="">jonesc@hep.phy.cam.ac.uk</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space" class="">Hi,<div class=""><br class=""></div><div class="">I might be wrong, but I do not believe it is possible to temporarily change the install prefix, for a single port.</div><div class=""><br class=""></div><div class="">Most probably you will need to start a new installation, using a custom installation prefix, from scratch. see</div><div class=""><br class=""></div><div class=""><a href="https://www.macports.org/install.php#source" target="_blank" class="">https://www.macports.org/install.php#source</a></div><div class=""><br class=""></div><div class="">on installing from source, which you will need to do to change the installation prefix, as its a configure time option.</div><div class=""><br class=""></div><div class="">Chris<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 17 Jan 2020, at 9:33 pm, Dave Allured - NOAA Affiliate via macports-users <<a href="mailto:macports-users@lists.macports.org" target="_blank" class="">macports-users@lists.macports.org</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">I am on a corporate network with ports installed normally in /opt/local, controlled by system admins. Users do not have any write access into system directories. I would like to use a local portfile repository in user space, as described in Macports guide 4.6.<br class=""><br class="">How can I test ports in the local repository? The "portindex" command works as expected in this directory. However, "port install" fails with "Insufficient privileges to write to MacPorts install prefix". I need a way to tell "port install" to use a local prefix, rather than the default system prefix, for only the port under test.<br class=""><br class="">I figured that I could avoid tampering with the protected sources.conf, by manually pre-staging the desired distfiles in the local repository. Here is my embryonic directory structure:<br class=""><br class="">$HOME/portx/science/netcdf-fortran/Portfile<br class="">$HOME/portx/science/netcdf-fortran/files/patch-Makefile.in.diff<br class="">$HOME/portx/var/macports/distfiles/netcdf-fortran/netcdf-fortran-4.5.2.tar.gz<br class=""><br class="">Thank you for any advice.</div></div></blockquote></div></div></div></blockquote></div></div>
</div></blockquote></div><br class=""></body></html>