public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
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	[thread overview]
Message-ID: <B9D8FAAC-2FE0-4F32-9889-54D860DB1DD7@ipfire.org> (raw)
In-Reply-To: <172536495220.111584.3859812822398819080@mail02.haj.ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

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 src/ or config/. Otherwise, if you extract a tarball in /usr/src you can modify the source as you like.

It would be more helpful if you sent us logs of the error where your build breaks.

-Michael

> On 3 Sep 2024, at 14:02, sio / <siosios1(a)hotmail.com> wrote:
> 
> hi all,
> 
> I've been playing around with building the netdata package and it seems that in the build environment there is not a way to chmod or run a .sh  file (from the lfs file) that is needed to build netadata. Is this by design or is there something I am missing? i have the lfs file setup to download all the resources per the offline install guidelines but it still requires their .sh file to run.


      reply	other threads:[~2024-09-04  7:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 12:02 sio /
2024-09-04  7:10 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B9D8FAAC-2FE0-4F32-9889-54D860DB1DD7@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox