Well, when a package is made "obsolete" by another (newer) one, we're telling the packaging system that the newer one is a compatible replacement for the older one, right? In this case, that's not true. Python 2.7 is not a compatible replacement for Python 2.6. With it marked obsolete, IPS actually makes it difficult to install the older version along side. I think that's a mistake.
Would it not have been enough to remove Python 2.6 from the userland consolidation? (so it's only installed if I actually ask for it?) Disappointed... On Fri, May 12, 2017 at 12:29 AM, Alexander Pyhalov <a...@rsu.ru> wrote: > Hi. > > On 12.05.2017 02:14, Gordon Ross wrote: >> >> I've been trying out the latest OI build, and most things look great! >> (Thanks to everyone who helped.) >> >> However, I have some 3rd party stuff that wants older versions of perl >> (5.10.0, 5.16) and python (2.6) and I can't figure out how to get pkg >> to let me install those along side the current ones (perl 5.22, python >> 2.7). >> Some time ago, it was possible to install multiple versions of perl >> and/or python. >> Is that still possible? > > > It's still possible to have python 2.7 and 3.4 or perl 5.22 and 5.24 > coinstalled, > but older versions were marked 'Obsolete', which means IPS will refuse to > install > them and will attempt to remove as long as there's no installed dependent > packages. > I suppose, you understand, why we don't want to have software, which is not > longer > supported by projects itself in our repository. > > From other packages which I'd like to mark Obsolete I see all MySQL(percona, > mariadb) versions > before 5.7 and PostgreSQL 9.3 (perhaps, 9.4)... > --- > System Administrator of Southern Federal University Computer Center > _______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev