On 2018-12-10 11:07 a.m., Michał Górny wrote: > What can we do to solve it? > =========================== > > a) Do nothing and hope upstreams solve it at some point. I don't think > this is acceptable because Portage's slowdown is going to be > significant. > > b) Start dropping py2 from packages. Sadly, this is hard because we're > talking about huge reverse dependency graph, and I'm pretty sure some of > our users need those packages w/ py2 support. > > c) Slot IPython? That's probably the least intrusive option, though > ugly as hell, and I'm not sure if it's not going to impact dep > calculation severely anyway. We'd have a :5 slot that supports py2 > only, and :0 slot that supports py3 only. Dependencies will be tricky, > life's going to be hard but maybe things will work. > > Any other options?
This'll be uglier for maintainers but cleaner for the repo -- what about a single IPython "package" that installs :5 for py2 and :0 for py3 ? Since python multi-builds anyways it shouldn't be too difficult to have it install from separate distfiles. Versioning would be a royal pain, likely some sort of combination of versions into a snapshot version number of sorts would need to be done...
signature.asc
Description: OpenPGP digital signature
