Laszlo (Laca) Peter wrote: > The background of this question if that I'm working on > updating Python to 2.5. For a period of time, we would > have to ship 2 versions of Python simultaneously: 2.4 > and 2.5. We have 2 obvious choices: > a) ship 2.4 in one package and 2.5 in another > b) ship both versions in one package > > In S10, we're doing b) (with 2.3 and 2.4) but I don't > really like it. As we're moving away from the older version, > ideally, it should only be installed if something needs it. > > a) is always an option, but I'm hoping that there is > some way to avoid having to incorporate some of the > versioning in the package name. SVr4 allows installing > 2 instances, so in theory, one could install > SUNWPython version 2.4.4 and SUNWPython version 2.5.2 > on the same system, since there won't be any conflicting > files. It wouldn't play nicely with upgrades, though. > And it's also not an option for Nevada integration. > > So the question is, what's the recommended way to handle > this with pkg(5)?
Are 2.4 and 2.5 compatible? I assume no, otherwise this wouldn't be an issue, right? How do you propose to handle external dependencies, or are we going to assume that that isn't an issue? E.g., if a package depends on SUNWpython, it's ok to install 2.5 instead of 2.4. Right now we don't have dependencies on python 2.4 - they're on SUNWpython. What is /usr/bin/python going to be? IPS doesn't support installing different versions of the same package at the same time. - Bart -- Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
