On 2014-02-16 22:23, mk-macpo...@techno.ms wrote:
> There is still one big problem with all of this, which is that a ton of
> daemons and agents might be running as root or as another user for a given
> MacPorts installation.
It's not only the daemons running, but also the symlinks in the
direct
On 2014-2-17 15:07 , Ryan Schmidt wrote:
>
> On Feb 16, 2014, at 14:29, Sean Mehta wrote:
>
>> To make a parallel installation for testing, I compile from source with
>> something like:
>>
>> $ ./configure --prefix=$MP_PREFIX
>> --with-applications-dir=$MP_PREFIX/Applications \
On Feb 16, 2014, at 14:29, Sean Mehta wrote:
> To make a parallel installation for testing, I compile from source with
> something like:
>
> $ ./configure --prefix=$MP_PREFIX
> --with-applications-dir=$MP_PREFIX/Applications \
> --with-tclpackage=$MP_PREFIX/Lib
> At that point, it might take as long as a reboot depending on your build: but
> you should achieve the same outcome.
I guess you’re right. :)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo
Eh, then prior to switching symlinks you ought to port unload all installed
packages and then deactivate them, then switch and install and load all those
packages.
At that point, it might take as long as a reboot depending on your build: but
you should achieve the same outcome.
On Feb 16, 2014
On 16 Feb 2014, at 22:25 , Jeremy Lavergne wrote:
> You could reboot after each switch: anything that’s no longer linked into
> /opt/local won’t load, and everything else will launch the appropriate
> version.
Yes, that’s possible, but to "M$ Windows"-like! ;-)
You could reboot after each switch: anything that’s no longer linked into
/opt/local won’t load, and everything else will launch the appropriate version.
On Feb 16, 2014, at 16:23, mk-macpo...@techno.ms wrote:
> There is still one big problem with all of this, which is that a ton of
> daemons a
There is still one big problem with all of this, which is that a ton of daemons
and agents might be running as root or as another user for a given MacPorts
installation.
In case I want to swap in another installation, say a debug installation, I
would have to make sure that all these services w
On 16 Feb 2014, at 21:46 , Jeremy Lavergne wrote:
> But I am assuming macports can handle being inside a symlink since I recall
> it can operate across drives.
Thanks, Jeremy.
That seems to be a good approach.
Greets,
Marko
___
macports-dev mailing l
You might consider linking different directories to /opt/local for your various
parallel installs. You’d similarly link other directories you need as well. The
whole operation could be part of a bash function or alias to replace all the
links.
But I am assuming macports can handle being inside
Thanks, Sean!
On 16 Feb 2014, at 21:29 , Sean Mehta wrote:
> $ ./configure --prefix=$MP_PREFIX
> --with-applications-dir=$MP_PREFIX/Applications \
> --with-tclpackage=$MP_PREFIX/Library/Tcl
I knew that this trick would work, because I used that in the past with m
Hey,
> That doesn't mean that a rogue port couldn't install something outside
> of $MP_PREFIX, but I've never noticed anything installed outside of
> $MP_PREFIX with the ports I've installed.
There are some ports that deliberately install files outside $MP_PREFIX, but to
my knowledge those are o
To make a parallel installation for testing, I compile from source with
something like:
$ ./configure --prefix=$MP_PREFIX
--with-applications-dir=$MP_PREFIX/Applications \
--with-tclpackage=$MP_PREFIX/Library/Tcl
$ make
$ sudo make install
w
I just wanted to set up a 2nd parallel MacPorts install - as I used to have it
before moving to Mavericks…
Now I realise that it is probably not a good idea to have a setup like that
after all.
Some applications install themselves into /Applications and have settings in
/Library…
Assuming I h
14 matches
Mail list logo
