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
Subject: Re: [gentoo-dev] Re: [RFC] Splitting dev-lang/python into per-slot packages, starting with 3.14
Date: Sat, 12 Oct 2024 15:07:14 +0200	[thread overview]
Message-ID: <10494e1714a04e1eb66d8790a7d0c5fa3bac5023.camel@gentoo.org> (raw)
In-Reply-To: <Zwprz8lSQcLQbk5Q@sysrq.in>

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

On Sat, 2024-10-12 at 17:30 +0500, Anna (cybertailor) Vyalkova wrote:
> On 2024-10-12 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?
> 
> Absolutely no, and your proposal seems to solve the shortcomings of 
> slotting given the limitations. Just Python is not the only language 
> with multiple simultaneous versions supported in Gentoo (Ruby comes to 
> mind first), and it opens a slippery slope.

I still find this weak, compared to ~20k packages in Gentoo right now.

> Is there anything that makes Python unique enough to stand out from 
> conventions estabilished for packaging other languages? Or would it 
> essentially lead to a new policy?

Python pretty much sets the quality standards for Gentoo these days.

-- 
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:07 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 [this message]
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
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=10494e1714a04e1eb66d8790a7d0c5fa3bac5023.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --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