Re: Problem using a second pkgsrc unprivileged

[Sad Clouds <cryintothebluesky%gmail.com@localhost>]

On Sun, 25 Oct 2020 10:46:13 -0400
Greg Troxel <gdt%lexort.com@localhost> wrote:

> 
> Connor McLaughlan <cont6pro3%gmail.com@localhost> writes:
> 
> > One out of several usecases i have is to get some old kde3/qt3 stuff
> > compiled and running.
> > It will run in a clean old pkgsrc-tree, but i am unable to install
> > those old libraries into a current pkgsrc-tree, due to file
> > conflicts.
> 
> You should be able to this.  Lack of containers is a red herring, I
> think.  You may have to fix bugs, but it may also be that your only
> real issue is BINPKGS.

I don't think it's as simple as that. Some software is quite complex
and can result in run-time conflicts. For example, you want to run V1.0
and V2.0 of the same software at the same time. So you manage to
install them in different locations, but you can't run two instances at
the same time, because they share things like - log and db files, pid
and lock files, IPC paths like unix sockets and shared memory, and so
on. You need zones or containers, which could be emulated with chroot
to some extent.