Yes, I think you are. Basically if you build an RPM, it does the ./configure; make && make install. Geerally FOSS packages default to /usr/local and distro's configure them to be rooted at /, /usr, /opt whatever.
So in fact you ought to be able to be able to build Gen++ packages, rooted at a different place than Gen, and select which implementation you use by traditional means $PATH & environment.
Opening up openSUSE 11.2 Software Package manager, and I find :
So perhaps Distro's with good package managers are not the problem at all.
Whoops I just installed python3 without really meaning to, expecting it to tell me about other packages it would require installed to with it.
I have both installed, guessing it'll be python3 :
ladm@fir:~/.kde4/share/config> python3
Python 3.1 (r31:73572, Oct 24 2009, 05:39:09)
[GCC 4.4.1 [gcc-4_4-branch revision 150839]] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
Multiple versions of the same package installed at same time
Posted Nov 13, 2009 16:18 UTC (Fri) by Cato (subscriber, #7643)
[Link]
I think you've made my point for me, which was that installing a second
version is significantly more complex than just installing the default
version.
I'm aware that some distros create 'python3' packages, but that's really a
hack rather than a general solution - why isn't it possible to pull a newer
version of Python from a later version of the distro (e.g. Ubuntu 9.10 while
using an earlier version of Ubuntu), and cleanly install it with
dependencies, maybe in a dynamically created chroot or simply a new directory
prefix.
Multiple versions of the same package installed at same time
Posted Nov 14, 2009 17:35 UTC (Sat) by man_ls (subscriber, #15091)
[Link]
It is better this way, I think. I don't want a second set of the same libraries lying around; if I did I would do the chroot myself. It does not look like a hack to me, at least on Debian.