Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Topics for the Buildroot Developers meeting
Date: Mon, 29 Oct 2012 23:38:15 +0100	[thread overview]
Message-ID: <20121029233815.62dad9b3@skate> (raw)
In-Reply-To: <CABYt4-a-3ozfyg-6dRg35vSAv-u8czNyi4cZ=QngtAND0jhcyA@mail.gmail.com>


On Mon, 29 Oct 2012 18:30:01 -0400, Shawn Goff wrote:
> From the discussion page:
> > Make it possible to do a 'target-clean', as a replacement of uninstall. Will this even work at all? Proposed by Arnout Vandecappelle
> 
> This would be amazing.
> 
> I had a quick chat in #ptxdist today, and it seems that's what they do
> - they have separate stages, including a compile, install, and
> targetinstall. The install installs the package into a
> project-specific directory, and targetinstall creates an ipkg and
> installs the package's relevant files to the root filesystem. When you
> need to remove a package, you unselect it from the config and rebuild
> the rootfs.

Except that it doesn't work properly, even in PTXdist (as far as I
know, of course). We had a discussion about this last year at ELCE with
PTXdist developers. Basically, do the following:

 * Build program foo with OpenSSL support (the OpenSSL support in foo
   is optional, foo can work without OpenSSL). Both foo and openssl are
   installed in the target.

 * Enjoy foo with OpenSSL on your target, you're happy.

 * Now, remove OpenSSL from your target.

Beng, "foo" no longer works, because a library it is linked against no
longer exists, and "foo" has not been rebuilt without OpenSSL support.
As far as I know, PTXdist doesn't keep track of reverse dependencies
when removing a package, and that can lead to invalid root filesystems.

That's the precise reason why we decided /not/ to support packages in
Buildroot: solving this problem completely is very complicated, and we
thought it is better to not solve the problem than to solve it in half.

We detailed all this in our ELCE 2011 meeting report, but I guess we
should make it part of our FAQ because it is actually a FAQ :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-10-29 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 18:43 [Buildroot] Topics for the Buildroot Developers meeting Thomas Petazzoni
2012-10-29 20:23 ` Danomi Manchego
2012-10-29 22:30 ` Shawn Goff
2012-10-29 22:38   ` Thomas Petazzoni [this message]
2012-10-30  0:26     ` Shawn Goff
2012-11-01  9:26     ` Robert Schwebel

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=20121029233815.62dad9b3@skate \
    --to=thomas.petazzoni@free-electrons.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