Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boot/barebox: add renaming functionality to barebox image copy
Date: Fri, 22 Feb 2019 11:19:58 +0100	[thread overview]
Message-ID: <20190222111958.68393178@windsurf> (raw)
In-Reply-To: <ef5bbef6-02e5-7c44-bec1-f65896df581f@mind.be>

Hello,

On Fri, 22 Feb 2019 09:53:18 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:

>  Indeed, this use case happens to (almost) work by chance because barebox and
> barebox-aux are two different packages rather than one like for U-Boot. But if
> you anyway have the luck of having such an option, I don't mind adding a little
> bit extra to be able to make better use of it.
> 
>  Perhaps a possibility is to add a config option that prefixes the output name
> with something? You'd still need to rename it in the post-build script (or, more
> likely, handle that in the genimage.cfg file). But it does solve the
> identical-name problem, it looks pretty simple, and it doesn't break anything.

Good idea! It is simple (just one string option), and it preserves
backward compatibility (the default value of the option would be empty).

Markus, could you look at implementing this instead ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-02-22 10:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 11:03 [Buildroot] [PATCH 1/1] boot/barebox: add renaming functionality to barebox image copy Steinhilber, Markus
2019-02-22  8:40 ` Thomas Petazzoni
2019-02-22  8:53   ` Arnout Vandecappelle
2019-02-22 10:19     ` Thomas Petazzoni [this message]
2019-02-25 10:00       ` Steinhilber, Markus
2019-02-25 10:20         ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2019-02-18 13:59 Steinhilber, Markus
2019-02-18 22:10 ` Thomas Petazzoni

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=20190222111958.68393178@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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