From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Problem building a python3 package in IPFire3 Date: Thu, 28 Sep 2023 10:16:52 +0100 Message-ID: <818170B6-01DE-43E8-A7DE-C9A530DF1A8A@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3395053158623067223==" List-Id: --===============3395053158623067223== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 22 Sep 2023, at 15:00, Adolf Belka wrote: >=20 > Hi All, >=20 > I was looking at updating python3-markdown in IPFire3. However that version= no longer has a setup.py file. It only has a pyproject.toml file. >=20 > In IPFire2 we dealt with that by installing python3-build which had a setup= .py file and then using >=20 > python3 -m build \ > --no-isolation \ > --wheel >=20 > for the build part and >=20 > pip3 install \ > --no-build-isolation \ > --root=3D"/" \ > --no-deps \ > --ignore-installed \ > dist/*.whl >=20 > for the install part. >=20 > However build is now version 1.0.3 and since version 1.0.0 it no longer has= a setup.py file in it, only a pyproject.toml file and you can't use build to= build build until build has been installed!!!!! >=20 > The instructions for build says that you have to use pip to install build, = although it is not clear if that will work without internet. > The above build and install worked for IPFire2 because the build stage used= python3-build to create a wheel from the source file and then pip to install= the generated wheel file and none of that needed to load things from the int= ernet. Well, this is a classic bootstrapping dilemma. We have this in many places: F= or example you will need a C compiler to build GCC, which is our C compiler. = The Rust toolchain also has this problem and can not be bootstrapped without = a rust compiler. In IPFire 2 this is usually a big disaster and we used to build some packages= with only some minimal parts, then build something else that depended on it,= and the built the first package in all its full glory again. This is obvious= ly complicated and breaks all the time - as well as wasting CPU cycles. Curre= ntly we only do this with libstdc++: https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dmake.sh;h=3Dacb6921= 403bf868128f1810a7e9bbafae13fc10e;hb=3DHEAD#l987 It is the GCC being built with PASS=3DL (L being short for libs). Back to the original problem=E2=80=A6 This might be fun, but IPFire 3 should = make this easier. You could start by building the older version of python3-bu= ild that still comes with setup.py. The update the package to its later versi= on and make it depend on itself. That way, you have all the tools available t= o build the next version for python3-build. This normally works well except t= hat we will have a nightmare when we bootstrap IPFire for yet another archite= cture, but as things stand right now, that won=E2=80=99t happen anytime soon. > I am not sure how to deal with this now. This will also be a problem for IP= Fire2 if we want to bring the various python3 packages up to date. >=20 > I had a look at what Arch Linux were doing to build the python3-build packa= ge and they have a makedepends of python-build to build python-build, which I= don't understand how it would work. See above :) If this works, please submit two patches with one for each versi= on so that we can recreate this in the build service. -Michael > Looking forward to any suggestions. >=20 > Regards, >=20 > Adolf. >=20 > --=20 > Sent from my laptop >=20 --===============3395053158623067223==--