From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Where does post-build script belong?
Date: Fri, 16 Mar 2012 22:32:22 +0100 [thread overview]
Message-ID: <87ehssp6zd.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LUS+aYLQ3vneJKJMd+4TNQ6UGH+rAywr4k6C1Z4AXe7Pg@mail.gmail.com> (Thomas De Schampheleire's message of "Wed, 29 Feb 2012 08:41:07 +0100")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> writes:
Hi,
>> ?If you ask me, BR2_ROOTFS_SKELETON_CUSTOM_PATH is indeed useless and
>> should be deprecated.
Thomas> Although I'm not using it myself, I don't think this needs to be
Thomas> deprecated. I can imagine that there are users who have a
Thomas> significantly different skeleton that it would be a nuisance to have
Thomas> to tweak it from a script.
Thomas> Although we may recommend in the docs to use the post-build script +
Thomas> rootfs-additions, I would keep the custom option as well.
Agreed. It doesn't add much complexity to BR, and we've had it for a
very long time, so chances are people are using it (E.G. I know some
people at work do).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-03-16 21:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 20:41 [Buildroot] Where does post-build script belong? Grant Edwards
2012-02-20 21:00 ` J.C. Woltz
2012-02-20 21:45 ` Grant Edwards
2012-02-21 8:44 ` Luca Ceresoli
2012-02-21 14:54 ` Grant Edwards
2012-02-28 20:38 ` Arnout Vandecappelle
2012-02-28 21:06 ` Grant Edwards
2012-02-28 21:29 ` Steve Calfee
2012-02-28 21:36 ` Grant Edwards
2012-02-28 22:06 ` Steve Calfee
2012-02-28 22:18 ` Grant Edwards
2012-03-16 21:30 ` Peter Korsgaard
2012-02-28 22:19 ` Arnout Vandecappelle
2012-02-29 7:41 ` Thomas De Schampheleire
2012-03-16 21:32 ` Peter Korsgaard [this message]
2012-02-28 22:18 ` Arnout Vandecappelle
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=87ehssp6zd.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.