From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: How to deal with consequences of update to attr Date: Mon, 08 Feb 2021 13:21:49 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0311723446299688907==" List-Id: --===============0311723446299688907== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, I am trying to keep up with all your emails. So forgive me if it takes a litt= le while :) > On 8 Feb 2021, at 09:01, Adolf Belka (ipfire-dev) wrote: >=20 > Hi all, >=20 > I found that attr was from 2013 but that there was a newer update from 2018= , so I ran a build of the update which worked fine. >=20 > However python-xattr failed to build because xattr.h was not provided by th= e new version of attr. I realised that python-xattr-0.5.0 was from 2007 so re= ally needed updating also. Interesting that so much has changed in this package. I would say that we should drop python-xattr. It was needed for pakfire 3 whi= ch no longer depends on this python module. On top of this, this is a Python = 2 module and since Python 2 is EOL we should start to remove them all one by = one. Software needs to be ported to Python 3 and we will need to remove Pytho= n 2 entirely at least from the installed system - it might be needed in the b= uild environment. > Ran the build for python-xattr-0.9.7 from 2019. However it required python-= cffi. So I added that. python-cffi also requires python-setuptools, which is = available as an addon so I just had to adjust the order of the build to inclu= de that. Then had to add python-pycparser as that is also required by python-= cffi. >=20 > After all of the above the package completed building without any errors. >=20 > My question is about the additional required python packages cffi (C Foreig= n Function Interface) and pycparser (Complete parser for C acting as a front = end for C Compilers or analysis tools). >=20 > It doesn't seem like they should need to be added as addons just so that py= thon-xattr can be built. It would make more sense to me to add them only for = the building portion. Presumably I place the required programs into the build= base section of make.sh but how do I ensure that they are only used in the bu= ild and not also included in the final IPFire. >=20 > I see that meson is in the buildbase section and is not in the final IPFire= but gzip is also in the buildbase section but does end up in the final IPFir= e but I can't see what I need to specify to make sure the additional python p= ackages follow the meson approach and not the gzip approach. I suspect it wil= l turnout to be obvious but I have not been able to figure it out. Yes, loads of tools will not be shipped with the system because they are not = needed there and we try to keep IPFire as small as possible - within reason. = So they could have been a package just like meson or binutils, but since nobo= dy is using the python-xattr module any more, it would be better to remove it. -Michael >=20 > Help required please on how to go about this. >=20 >=20 > Thanks and regards, >=20 > Adolf. >=20 > --=20 > Sent from my desktop >=20 --===============0311723446299688907==--