All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Developer Day
Date: Tue, 15 Nov 2011 22:17:08 +0000	[thread overview]
Message-ID: <201111152217.08212.arnout@mind.be> (raw)
In-Reply-To: <20111102160349.4afe5935@skate>

On Wednesday 02 November 2011 15:03:49 Thomas Petazzoni wrote:
> On the feature that is often discussed on the Buildroot list, and
> which was on the agenda for this meeting was the general topic of
> "package management". To summarize, the idea would be to add some
> tracking of which Buildroot package installs what files, with the
> goals of :
> 
>  * Being able to remove files installed by a package when this package
>    gets unselected from the menuconfig ;

 I completely agree with the final conclusion that this is almost impossible to 
achieve in a simple, consistent and reliable way.  Something that would help a 
lot for that purpose, however, is to have a 'make clean-target' target.  This 
would wipe $(TARGET_DIR) and remove all .stamp_target_installed files.  The 
next build will re-copy the skeleton and reinstall all packages, which should 
be sufficient and shouldn't take very long.  clean-staging would also be nice 
but is probably a bit more difficult to implement because of the toolchain.


>  * Ultimately, be able to generate binary packages (ipk or other
>    format) that can be installed on the target without re-generating a
>    new root filesystem image.

 Now this, on the other hand, is still a useful addition.  At least, if it 
doesn't make the build system much more complicated to add it (you probably 
need at least a per-package staging dir).


 Regards,
 Arnout


-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  31BB CF53 8660 6F88 345D  54CC A836 5879 20D7 CF43

  parent reply	other threads:[~2011-11-15 22:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 15:03 [Buildroot] Report from the Buildroot Developer Day Thomas Petazzoni
2011-11-02 20:15 ` Peter Korsgaard
2011-11-04 11:56 ` Luca Ceresoli
2011-11-04 12:30   ` Michael S. Zick
2011-11-07 16:17   ` Peter Korsgaard
2011-11-07  9:58 ` Thomas De Schampheleire
2011-11-07 12:09   ` Sam Ravnborg
2011-11-07 12:25     ` Thomas Petazzoni
2011-11-07 12:39       ` Yann E. MORIN
2011-11-08 13:20         ` Thomas De Schampheleire
2011-11-07 12:39   ` Thomas Petazzoni
2011-11-07 19:01     ` Yann E. MORIN
2011-11-08  8:19       ` Thomas De Schampheleire
2011-11-15 22:17 ` Arnout Vandecappelle [this message]
2011-11-15 23:28   ` Michael S. Zick
2011-11-17 13:57   ` Thomas De Schampheleire
2011-11-17 21:21     ` Bjørn Forsman
2011-11-18  6:39       ` Thomas De Schampheleire
2011-11-18 11:04         ` Bjørn Forsman
2011-11-18 11:36           ` Thomas De Schampheleire
2011-11-18 17:51           ` Arnout Vandecappelle
2011-11-18 22:53             ` Peter Korsgaard
2011-11-18 23:16               ` Arnout Vandecappelle
2011-11-19  8:24                 ` Peter Korsgaard
2011-11-20  8:36             ` Thomas Petazzoni
2011-11-20  9:58               ` Peter Korsgaard

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=201111152217.08212.arnout@mind.be \
    --to=arnout@mind.be \
    --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.