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] Re: [RFC] Splitting dev-lang/python into per-slot packages, starting with 3.14
Date: Sat, 12 Oct 2024 15:03:56 +0200	[thread overview]
Message-ID: <96e7428bf48fbc96d02f8f65edfe91888f8da831.camel@gentoo.org> (raw)
In-Reply-To: <1a1f9b9f-7428-4536-847c-e6965336b451@gentoo.org>

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

On Sat, 2024-10-12 at 15:00 +0200, Luca Barbato wrote:
> On 12/10/24 11:13, Michał Górny wrote:
> > On Sat, 2024-10-12 at 10:50 +0200, Luca Barbato wrote:
> > > On 12/10/24 10:12, Michał Górny wrote:
> > > > Comments?
> > > > 
> > > I'm afraid it would lead to way too many packages and I'm not sure the
> > > overall experience would be an improvement.
> > 
> > 5 are too many?
> 
> potentially it is python_{version}_{variants} so at least 10*2 assuming 
> we keep around 3.{N..N+5} and we have two worthy variants.
> 
> Plus the chore of treecleaning older packages. Not sure if it is worth it.

That sounds like an advantage, actually.  Currently, we keep older
versions for a long time, then they suddenly disappear.  All the things
considered, perhaps we ought to verbosely last rite them.

> > In fact, even today "emerge dev-lang/python" is probably a bad solution,
> > as it will lead to a beta/rc version on an ~arch system most
> > of the time.
> > 
> > > An alternative for freethreading support wouldn't be to install both
> > > from the same package python-3.14 and have the two PYTHON_TARGETS ?
> > 
> > I don't understand.
> 
> emerge =python-3.14 would install both a non-freethreading and a 
> freethreading version and it would satisfy 3_14 and 3_14t at the same.
> 

But that's not how PMs work?  It would install only the "newer" version,
which would probably mean freethreading, which is not what people
usually want.

-- 
Best regards,
Michał Górny


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

  reply	other threads:[~2024-10-12 13:04 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 [this message]
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
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=96e7428bf48fbc96d02f8f65edfe91888f8da831.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