On Fri, Mar 21, 2025 at 9:33 AM Michał Górny wrote:
> Hello, everyone.
>
> TL;DR: I'm thinking of shutting down all gentoo-mirror repositories,
> except for gentoo and guru.
>
>
> Over 10 years ago, I've started the repository mirror & CI project.
> What started as a bunch of shell scripts on a u
n, slot would indicate PyPy
> 3.x slot and subslot would indicate the ABI (changes rarely).
>
Previously, you "split the packages even further", but now you're
suggesting to "recombine all these packages into one". What was the
original reason for splitting the packages, and what has changed since then?
I don't understand enough of the Python and PyPy infrastructure to support
or object to either approach. I generally think it's more elegant to have a
single package for a single codebase/project, but the practical concerns
are more important.
- Mitchell Dorrell
>
On Sat, Oct 12, 2024, 14:03 Michał Górny wrote:
> On Sat, 2024-10-12 at 10:12 +0200, Michał Górny wrote:
> > 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
How will the upgrade path look, from e.g. 3.16 to 3.17? What will the
typical Gentoo user experience be? What will the experience be for a Python
developer with a local overlay containing custom Python packages?
I didn't like this idea at first, but I'm warming up to it.
On Sat, Oct 12, 2024, 06:
On Sat, Oct 12, 2024, 06:23 Michał Górny 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
