From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Adolf Belka (ipfire-dev)" To: development@lists.ipfire.org Subject: Re: How to deal with consequences of update to attr Date: Mon, 08 Feb 2021 14:41:19 +0100 Message-ID: <71fa15a3-603e-7f95-517e-5cc2ea33046f@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4753684201918526016==" List-Id: --===============4753684201918526016== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 08/02/2021 14:21, Michael Tremer wrote: > Hello, >=20 > I am trying to keep up with all your emails. So forgive me if it takes a li= ttle while :) This one was only sent this morning so you replied quickly to it. I=20 understand if a reply takes longer so no problems. >=20 >> On 8 Feb 2021, at 09:01, Adolf Belka (ipfire-dev) wrote: >> >> Hi all, >> >> I found that attr was from 2013 but that there was a newer update from 201= 8, so I ran a build of the update which worked fine. >> >> However python-xattr failed to build because xattr.h was not provided by t= he new version of attr. I realised that python-xattr-0.5.0 was from 2007 so r= eally needed updating also. >=20 > Interesting that so much has changed in this package. >=20 > I would say that we should drop python-xattr. It was needed for pakfire 3 w= hich no longer depends on this python module. On top of this, this is a Pytho= n 2 module and since Python 2 is EOL we should start to remove them all one b= y one. Software needs to be ported to Python 3 and we will need to remove Pyt= hon 2 entirely at least from the installed system - it might be needed in the= build environment. >=20 >> 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 incl= ude that. Then had to add python-pycparser as that is also required by python= -cffi. >> >> After all of the above the package completed building without any errors. >> >> My question is about the additional required python packages cffi (C Forei= gn Function Interface) and pycparser (Complete parser for C acting as a front= end for C Compilers or analysis tools). >> >> It doesn't seem like they should need to be added as addons just so that p= ython-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 buil= dbase section of make.sh but how do I ensure that they are only used in the b= uild and not also included in the final IPFire. >> >> I see that meson is in the buildbase section and is not in the final IPFir= e but gzip is also in the buildbase section but does end up in the final IPFi= re but I can't see what I need to specify to make sure the additional python = packages follow the meson approach and not the gzip approach. I suspect it wi= ll turnout to be obvious but I have not been able to figure it out. >=20 > Yes, loads of tools will not be shipped with the system because they are no= t 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 no= body is using the python-xattr module any more, it would be better to remove = it. Okay, that is a simple solution. I will create a new patch with attr and=20 the removal of python-xattr. Regards, Adolf. >=20 > -Michael >=20 >> >> Help required please on how to go about this. >> >> >> Thanks and regards, >> >> Adolf. >> >> --=20 >> Sent from my desktop >> >=20 --=20 Sent from my laptop --===============4753684201918526016==--