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?