All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10386] Add an option to put all compiled executables that show up on target/ in staging/ as well
Date: Mon, 13 Apr 2020 23:51:23 +0000	[thread overview]
Message-ID: <bug-10386-163-b9flTxwTK4@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10386-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10386

Carlos Santos <unixmania@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|ASSIGNED                    |RESOLVED

--- Comment #2 from Carlos Santos <unixmania@gmail.com> ---
As discussed in patchwork[1]

The idea would be to ensure that all packages install in staging/,
always. Then, identify packages that have different commands for target/
and staging/ and make them identical. Finally, remove the target install
commands, and genreate it as a copy of staging at the beginning of the
target-finalize step.

https://patchwork.ozlabs.org/project/buildroot/patch/20191001013654.22298-2-unixmania at gmail.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2020-04-13 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 17:08 [Buildroot] [Bug 10386] New: Add an option to put all compiled executables that show up on target/ in staging/ as well bugzilla at busybox.net
2019-09-30 11:14 ` [Buildroot] [Bug 10386] " bugzilla at busybox.net
2020-04-13 23:51 ` bugzilla at busybox.net [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=bug-10386-163-b9flTxwTK4@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.