public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: python@gentoo.org
Subject: Re: [gentoo-dev] [RFC] Splitting dev-lang/python into per-slot packages, starting with 3.14
Date: Sat, 12 Oct 2024 12:05:24 +0200	[thread overview]
Message-ID: <a803173d36548bc195fc5586e1f0a9f936f9b885.camel@gentoo.org> (raw)
In-Reply-To: <u34l1zlnw@gentoo.org>

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

On Sat, 2024-10-12 at 11:59 +0200, Ulrich Mueller wrote:
> > > > > > On Sat, 12 Oct 2024, Michał Górny wrote:
> 
> > However, I think the cleanest way forward would be to stop slotting
> > CPython like this, and instead have a separate package for each version,
> > just like the vast majority of distributions do, i.e.:
> 
> >   dev-lang/python3_N
> 
> That other distributions do it that way is not an argument because most
> other distributions don't have slots.
> 
> > This naturally means that only the specific version requested (e.g. via
> > targets) would be installed, and no cross-slot autoupgrades would
> > happen.  Ideally, I'd like to start doing that with Python 3.14 whose
> > first alpha is expected next week.  Depending on how they handle
> > freethreading, we'd end up having the first or both of:
> 
> >   dev-lang/python3_14
> >   dev-lang/python3_14t
> 
> 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.

Greedy upgrade behavior makes sense when you have packages where :=
and :* operators are applicable.  It doesn't make sense when every
single dependency is expected to specify an explicit slot.  In fact,
when you are never supposed to depend on the package without specifying
a slot, why would you think slots are the right solution?

In fact, the "freethreading" variation already implies that there could
be more than one "slot" per package version.

It's as meaningless as having sqlite3 packaged as sqlite:3, or gtk that
is now randomly split between gtk+:2, gtk+:3 and gtk:4.

-- 
Best regards,
Michał Górny


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

  parent reply	other threads:[~2024-10-12 10:05 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 [this message]
2024-10-12 10:13     ` Ulrich Mueller
2024-10-12 10:22       ` Michał Górny
2024-10-12 11:23         ` Mitchell Dorrell
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=a803173d36548bc195fc5586e1f0a9f936f9b885.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=python@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