From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Building of packages that require a .sh file to be executed Date: Wed, 04 Sep 2024 09:10:51 +0200 Message-ID: In-Reply-To: <172536495220.111584.3859812822398819080@mail02.haj.ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5144200639221790041==" List-Id: --===============5144200639221790041== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Good morning, You can virtually do anything in the build environment. Including running any= scripts. What you cannot do is modify the checked out build source. So potentially you= might need to make your script executable in the source if it is stored in s= rc/ or config/. Otherwise, if you extract a tarball in /usr/src you can modif= y the source as you like. It would be more helpful if you sent us logs of the error where your build br= eaks. -Michael > On 3 Sep 2024, at 14:02, sio / wrote: >=20 > hi all, >=20 > I've been playing around with building the netdata package and it seems tha= t in the build environment there is not a way to chmod or run a .sh file (fr= om the lfs file) that is needed to build netadata. Is this by design or is th= ere something I am missing? i have the lfs file setup to download all the res= ources per the offline install guidelines but it still requires their .sh fil= e to run. --===============5144200639221790041==--