public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mitchell Dorrell <mwd@psc.edu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Splitting dev-lang/python into per-slot packages, starting with 3.14
Date: Sat, 12 Oct 2024 07:23:14 -0400	[thread overview]
Message-ID: <CAHqckJ2xyxPqyBvZsFB2R6wOmJWStFjn+=SMTG8qNmhm7P8MAA@mail.gmail.com> (raw)
In-Reply-To: <a9502aebdbfb9c5d88eb6c6f09152be56ba1b3ad.camel@gentoo.org>

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

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?

>

[-- Attachment #2: Type: text/html, Size: 2098 bytes --]

  reply	other threads:[~2024-10-12 11:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-12  8:12 [gentoo-dev] [RFC] Splitting dev-lang/python into per-slot packages, starting with 3.14 Michał Górny
2024-10-12  8:50 ` [gentoo-dev] " Luca Barbato
2024-10-12  9:13   ` Michał Górny
2024-10-12 12:30     ` Anna (cybertailor) Vyalkova
2024-10-12 13:07       ` Michał Górny
2024-10-12 13:00     ` Luca Barbato
2024-10-12 13:03       ` Michał Górny
2024-10-12 17:36         ` Luca Barbato
2024-10-12 13:12     ` Sam James
2024-10-12  9:49 ` [gentoo-dev] " Eray Aslan
2024-10-12  9:51   ` Michał Górny
2024-10-12  9:59 ` Ulrich Mueller
2024-10-12 10:03   ` Ulrich Mueller
2024-10-12 10:06     ` Michał Górny
2024-10-12 10:05   ` Michał Górny
2024-10-12 10:13     ` Ulrich Mueller
2024-10-12 10:22       ` Michał Górny
2024-10-12 11:23         ` Mitchell Dorrell [this message]
2024-10-12 11:49           ` Michał Górny
2024-10-12 15:01     ` Mitchell Dorrell
2024-10-12 15:10       ` Sam James
2024-10-12 17:21     ` Anna (navi) Figueiredo Gomes
2024-10-12 13:52 ` orbea
2024-10-12 14:32   ` Andreas Sturmlechner
2024-10-12 17:37 ` Nowa Ammerlaan
2024-10-12 18:03 ` Michał Górny
2024-10-12 22:57   ` Mitchell Dorrell
2024-10-14  0:43 ` Sam James
2024-10-14  3:49   ` Michał Górny
2024-10-14  4:09     ` Sam James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHqckJ2xyxPqyBvZsFB2R6wOmJWStFjn+=SMTG8qNmhm7P8MAA@mail.gmail.com' \
    --to=mwd@psc.edu \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox