Re: [gentoo-dev] [RFC] Splitting dev-lang/python into per-slot packages, starting with 3.14

["Michał Górny" <mgorny@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]

On Sat, 2024-10-12 at 07:23 -0400, Mitchell Dorrell wrote:
> On Sat, Oct 12, 2024, 06:23 Michał Górny <mgorny@gentoo.org> wrote:
> 
> > On Sat, 2024-10-12 at 12:13 +0200, Ulrich Mueller wrote:
> > > > > > > > On Sat, 12 Oct 2024, Michał Górny wrote:
> > > 
> > > > > IMHO this would abuse the package name for information that
> > absolutely
> > > > > doesn't belong there. It belongs in PV or SLOT.
> > > > > 
> > > > > To me it seems that you try to work around a problem (greedy upgrade
> > > > > behaviour) that should really be solved in the package manager.
> > > 
> > > > In my opinion, it's the other way around.  We have slots, that are a
> > fit
> > > > solution for packages that are roughly compatible between every major
> > > > release, and we keep abusing them for every single thing we can bend
> > > > enough to make it fit.
> > > 
> > > So are you saying that Python versions aren't "roughly compatible"
> > > between releases? Like, they're a completely different language?
> > 
> > They're not compatible in the sense "if I install package for
> > python3.12, it will work in python3.13", because every version uses
> > a separate package tree.  Upstream has effectively made every version
> > separate.  On top of that, the same "minor" version can have a PyPy
> > variation and a "freethreading" variation now.
> > 
> > --
> > Best regards,
> > Michał Górny
> > 
> 
> How will this affect ebuilds that can use any version of Python 3? Will it
> need a giant or-block in DEPEND?
> 

Ebuilds are forbidden from depending on dev-lang/python directly. 
Eclasses take care of generating correct dependency strings.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]