Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Easier adding of new packages / alsa-lib & utils
Date: Fri, 8 Jun 2007 08:22:26 +0200	[thread overview]
Message-ID: <007501c7a995$663af6b0$0302a8c0@atmel.com> (raw)
In-Reply-To: 20070607132945.GC4224@firebird.dresden.micronet24.de

> Hi,
> 
> the attachment contains two patches. The first one will rapidly shorten
> the Makefile to add a new package to the buildroot (at least for most
> packages), while being fully compatible to the standard way used up to
> now.

As I see it we lack two things in the build.
1) Ability to use backup sites if the main site is temporarily or permanently down.
2) Handling of distributions.    I.E. ability to specify which package version you 
    want to build in a way which is separated from the package build script.
3) Ability to generate binary packages which can be added/removed from 
    the root fs.

Any chance of looking into this?
An alternative to this patch could be to use the OpenWRT build script
which does (1) and (3) above.

OpenWRT seems to be a split from buildroot.
Is there a heated history here?

> While the Config.in follows the same rules, the Makefile for the new
> package provides only the NEEDED information to add the package. Let see
> on an example (Its nearly the same included in the second patch):
> 


Best Regards
Ulf Samuelsson 

  reply	other threads:[~2007-06-08  6:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 13:29 [Buildroot] Easier adding of new packages / alsa-lib & utils Benjamin Tietz
2007-06-08  6:22 ` Ulf Samuelsson [this message]
2007-06-08 17:47   ` Benjamin Tietz
2007-06-09  7:53     ` Ulf Samuelsson
2007-06-09 12:12       ` Benjamin Tietz
2007-06-09 13:32         ` [Buildroot] Easier adding of new packages / Distribution Benjamin Tietz
2007-06-09 19:53   ` [Buildroot] Easier adding of new packages / alsa-lib & utils Thomas Lundquist
2007-06-08 17:50 ` Benjamin Tietz

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='007501c7a995$663af6b0$0302a8c0@atmel.com' \
    --to=ulf@atmel.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