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] package/pkg-generic.mk: fix generation of package list in reinstall
Date: Thu, 5 Nov 2020 22:16:43 +0100	[thread overview]
Message-ID: <20201105221643.707bba76@windsurf.home> (raw)
In-Reply-To: <CAJ4jsaftvtdepjTQG_ROvX3PAgRmzKqD60+Gf3rLHhZ3EFiQvQ@mail.gmail.com>

On Thu, 5 Nov 2020 14:21:21 -0300
Carlos Santos <unixmania@gmail.com> wrote:

> > I'll try to think about the issue you've reported and see if I can come
> > up with some useful suggestions.
> >
> I understand but wouldn't be a bug if a host package installed things
> on the target directory and vice-versa? Maybe the right thing to do is
> to ensure that this does not happen.

This can certainly be debated, and it would clearly be nicer if only
host packages installed stuff in HOST_DIR, only the staging
installation steps installed things in STAGING_DIR, and only target
installation steps installed things in TARGET_DIR. Unfortunately, we're
not there for a number of packages I'm afraid.

For example, qt5 is a target package, but it installs all its host
tools in HOST_DIR, and splitting up into a host-qt5 package is clearly
not trivial.

Another example: the external toolchain packages are all target
packages, as they install the libraries/headers in STAGING_DIR, the
libraries in TARGET_DIR... but they also install the cross-compiler and
other cross-tools in HOST_DIR.

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

      reply	other threads:[~2020-11-05 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 14:04 [Buildroot] [PATCH] package/pkg-generic.mk: fix generation of package list in reinstall unixmania at gmail.com
2020-11-05 16:33 ` Thomas Petazzoni
2020-11-05 17:21   ` Carlos Santos
2020-11-05 21:16     ` Thomas Petazzoni [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=20201105221643.707bba76@windsurf.home \
    --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