On Wed, 2008-06-11 at 20:29 -0700, Bart Smaalders 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.
> Are 2.4 and 2.5 compatible? No. > I assume no, otherwise this wouldn't be an issue, right? 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. Hmm... There's also no way to say this package depends on python >= 2.4 and conflicts with python >= 2.5, right? So that leaves 2 package names as the only option. Perhaps something like system/languages/python/2.4 and system/languages/python/2.5 ? > What is /usr/bin/python going to be? We probably need an smf service that sets /usr/bin/python to the latest available python. > IPS doesn't support installing different versions of the > same package at the same time. Thanks, Laca _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
