[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#58587] [PATCH 00/14] Introducing pyproject-build-system.
From: |
Marius Bakke |
Subject: |
[bug#58587] [PATCH 00/14] Introducing pyproject-build-system. |
Date: |
Tue, 18 Oct 2022 23:51:47 +0200 |
zimoun <zimon.toutoune@gmail.com> skriver:
> Hi Marius,
>
> On Mon, 17 Oct 2022 at 22:06, Marius Bakke <marius@gnu.org> wrote:
>
>> I plan to eventually merge it with python-build-system instead of
>> keeping it separate. Thoughts?
>
> I would suggest to have a clear plan about this transition strategy. :-)
> I mean, if we go to two separated Python build-systems and then merge
> them, we have to write down the various steps; otherwise it could be
> quickly a mess.
>
> For example,
>
> 1. advertise about this new Python build-system
> 2. recommend only this new
> 3. only include package using this new
> 4. convert from old to new
> 5. remove old / rename old to new
>
> or whatever else. My concern is to have two build systems to maintain
> on the long term.
>
> Once something lands to master and the API, it is then hard to modify.
> Therefore, it appears to me better to draw beforehand the large lines of
> this transition plan.
I tried to address this in the attached documentation patch.
The idea is to:
* Recommend it for new packages in the 'guix' channel, mostly during
patch review.
* Once we are confident in the implementation, remove the "experimental"
status and recommend it in the documentation.
* Merge pieces of it into python-build-system as we go, such as sanity
check changes, using python-toolchain, etc.
* When we "know" that there won't be any major regressions, swap out
python-build-system with pyproject-build-system entirely and mark the
latter as deprecated.
Thoughts?
0001-doc-Document-pyproject-build-system.patch
Description: Text Data
signature.asc
Description: PGP signature
- [bug#58587] [PATCH 12/14] gnu: python-mypy-protobuf: Switch to pyproject-build-system., (continued)
- [bug#58587] [PATCH 12/14] gnu: python-mypy-protobuf: Switch to pyproject-build-system., Marius Bakke, 2022/10/17
- [bug#58587] [PATCH 08/14] gnu: weasyprint: Use pyproject-build-system., Marius Bakke, 2022/10/17
- [bug#58587] [PATCH 10/14] gnu: python-statmake: Use pyproject-build-system., Marius Bakke, 2022/10/17
- [bug#58587] [PATCH 13/14] gnu: python-tempora: Switch to pyproject-build-system., Marius Bakke, 2022/10/17
- [bug#58587] [PATCH 09/14] gnu: python-glyphslib: Use pyproject-build-system., Marius Bakke, 2022/10/17
- [bug#58587] [PATCH 11/14] gnu: python-ufolib2: Use pyproject-build-system., Marius Bakke, 2022/10/17
- [bug#58587] [PATCH 01/14] gnu: python-setuptools: Move to python-build., Maxim Cournoyer, 2022/10/27
[bug#58587] [PATCH 00/14] Introducing pyproject-build-system., zimoun, 2022/10/18
- [bug#58587] [PATCH 00/14] Introducing pyproject-build-system.,
Marius Bakke <=
- [bug#58587] [PATCH 00/14] Introducing pyproject-build-system., zimoun, 2022/10/19
- [bug#58587] [PATCH 00/14] Introducing pyproject-build-system., Marius Bakke, 2022/10/19
- [bug#58587] [PATCH 00/14] Introducing pyproject-build-system., Marius Bakke, 2022/10/19
- [bug#58587] [PATCH 00/14] Introducing pyproject-build-system., zimoun, 2022/10/20
- [bug#58587] [PATCH 00/14] Introducing pyproject-build-system., Marius Bakke, 2022/10/22
- [bug#58587] [PATCH v2 01/22] gnu: python-setuptools: Move to python-build., Marius Bakke, 2022/10/22
- [bug#58587] [PATCH v2 02/22] gnu: pypy: Move to separate module., Marius Bakke, 2022/10/22
- [bug#58587] [PATCH v2 03/22] gnu: python-pip: Move to (gnu packages python-build)., Marius Bakke, 2022/10/22
- [bug#58587] [PATCH v2 04/22] build-system: Add pyproject-build-system., Marius Bakke, 2022/10/22
- [bug#58587] [PATCH v2 05/22] news: Add entry for 'pyproject-build-system'., Marius Bakke, 2022/10/22