Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] post-build script is called before rootfs tweaking
Date: Mon, 28 Jan 2013 17:09:11 +0100	[thread overview]
Message-ID: <5106A2A7.7060201@relinux.de> (raw)
In-Reply-To: <50FAE5CE.5020004@relinux.de>

Am 19.01.2013 19:28, schrieb Stephan Hoffmann:
> Am 19.01.2013 19:19, schrieb Peter Korsgaard:
>>>>>>> "Stephan" == Stephan Hoffmann <sho@relinux.de> writes:
>>  Stephan> Hello,
>>  Stephan> buildroot's documentation says:
>>  >> In the Buildroot configuration, you can specify the path to a
>>  >> *post-build script*, that gets called /after/ Buildroot builds all the
>>  >> selected software, but /before/ the rootfs packages are assembled.
>>  Stephan> I understand this the way that the post-build script is called as the
>>  Stephan> last action before package assembly.
>>
>>  Stephan> Is this a bug or a feature? I'd prefer having the script
>>  Stephan> called after the target directory is completely set up.
>>
>> I would call it a bug. I recently fixed up a similar issue with the
>> passwd handling happening after the post-build script.
>>
>> Care to send a patch to fix it?
> I can try, but at the moment I am too busy. Maybe somewhere next week.
This seems to be fixed in the meantime. I had this problem a
distribution based on 2012.08.

Sorry, I should have tried with the latest version before bothering the
list.

Kind regards

Stephan

-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

      reply	other threads:[~2013-01-28 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 17:10 [Buildroot] post-build script is called before rootfs tweaking Stephan Hoffmann
2013-01-19 18:19 ` Peter Korsgaard
2013-01-19 18:28   ` Stephan Hoffmann
2013-01-28 16:09     ` Stephan Hoffmann [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=5106A2A7.7060201@relinux.de \
    --to=sho@relinux.de \
    --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