Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Editing filesystem files
Date: Thu, 10 Apr 2008 13:43:20 +0200	[thread overview]
Message-ID: <005b01c89b00$1630eeb0$ad289e86@LPSC0173W> (raw)
In-Reply-To: 20080409223102.GA4582@cloud.net.au


> Dependencies between files in the root and the target_skeleton would be
> preferable. This would detect everything other than file deletions.

Yes, but it would be quite heavy to put it all in a make file, with the risk 
of forgetting something. I'm okay with the idea of the root being rebuilt 
from scratch, but how do you trigger that ? As you say, even deleting it 
completely won't copy some of the skeleton back. What can we 'touch' to make 
this happen ?
-- 
Guillaume Dargaud
http://www.gdargaud.net/

  reply	other threads:[~2008-04-10 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 14:29 [Buildroot] Editing filesystem files Guillaume Dargaud
2008-04-09 11:47 ` Guillaume Dargaud
2008-04-09 22:31   ` Hamish Moffatt
2008-04-10 11:43     ` Guillaume Dargaud [this message]
2008-04-12  9:22       ` Hamish Moffatt

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='005b01c89b00$1630eeb0$ad289e86@LPSC0173W' \
    --to=dargaud@lpsc.in2p3.fr \
    --cc=buildroot@busybox.net \
    /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