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: Files in Rootfiles
Date: Sat, 28 Oct 2017 13:10:50 +0100	[thread overview]
Message-ID: <1509192650.2749.1.camel@ipfire.org> (raw)
In-Reply-To: <003001d34fdb$b26238d0$1726aa70$@ipfire.org>

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

Hi,

unfortunately there is no better way than doing a full rebuild of the
entire distribution. I usually do that over night or when I am really
sure that I won't need to change anything else on the same day.

It is not good at all but if that helps, IPFire 3 doesn't have
rootfiles any more. So long we will have to survive on what we have.

Best,
-Michael

On Sat, 2017-10-28 at 12:58 +0200, Wolfgang Apolinarski wrote:
> Hi everyone,
> 
> I really need to learn how to really find out which files need to go into the root files and which files are added by other packages.
> 
> If I upgrade a single package, I usually delete the log file and re-build ipfire (because this is way faster than re-building everything). Usually, the "changed rootfile" than shows up and (in case of apache) shows some unrelated file that has been added by another package down the road (which also means that if I clean and build, it will complain it can't find that file, if I add that file to the rootfile). So how do I REALLY find out which files belong in the rootfile other than unpacking the source and looking at the build file of the individual package (and somehow guessing what will show compiled where)?
> 
> Best regards,
> Wolfgang
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-10-28 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28 10:58 Wolfgang Apolinarski
2017-10-28 12: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=1509192650.2749.1.camel@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