Dave Allured wrote:
> Is there an easy way to get macports to go through the motions of "port
> install -s" for a single port, using macports infrastructure, and taking
> port dependencies from /opt/local, but writing only inside a user
> directory?
You can't install or activate without write
On Jan 19, 2020, at 17:47, Dave Allured wrote:
> Is there an easy way to get macports to go through the motions of "port
> install -s" for a single port, using macports infrastructure, and taking port
> dependencies from /opt/local, but writing only inside a user directory? This
> would
On Sat, Jan 18, 2020 at 3:20 AM Mojca Miklavec wrote:
> On Fri, 17 Jan 2020 at 23:44, Christopher Jones
> wrote:
> > On 17 Jan 2020, at 10:36 pm, Dave Allured - NOAA Affiliate via
> macports-users wrote:
> >
> > Chris, thanks for the quick reply. You are correct, a private macports
>
On Fri, 17 Jan 2020 at 23:44, Christopher Jones
wrote:
> On 17 Jan 2020, at 10:36 pm, Dave Allured - NOAA Affiliate via macports-users
> wrote:
>
> Chris, thanks for the quick reply. You are correct, a private macports
> installation would enable testing ports without special privilege.
> On 17 Jan 2020, at 10:36 pm, Dave Allured - NOAA Affiliate via macports-users
> wrote:
>
> 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
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.
However, I would like to find an intermediate solution that avoids full
Hi,
I might be wrong, but I do not believe it is possible to temporarily change the
install prefix, for a single port.
Most probably you will need to start a new installation, using a custom
installation prefix, from scratch. see
https://www.macports.org/install.php#source
