Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Support for "distributions" in buildroot
Date: Sat, 21 Jul 2007 20:42:52 +0200	[thread overview]
Message-ID: <20070721184252.GA2523@zelow.no> (raw)
In-Reply-To: <044b01c7cb1e$8db0a550$dcc4af0a@atmel.com>

On Sat, Jul 21, 2007 at 12:34:36AM +0200, Ulf Samuelsson wrote:
> 
> Your suggestions means that either the end customer will get
> a buildroot frozen at a certain time, or that the maintenance
> effort to keep buildroot up to date has to be duplicated.

I believe in frozen snapshots instead of specifying source versions.

The rest of buildroot are also in so much flux that only being able to
specify source package versions is just a small part to the solution.

Patches are added, build system changed and so on.



Thomas.

  reply	other threads:[~2007-07-21 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 12:30 [Buildroot] [RFC] Support for "distributions" in buildroot Ulf Samuelsson
2007-07-20 14:04 ` Steven J. Hill
2007-07-20 22:34   ` Ulf Samuelsson
2007-07-21 18:42     ` Thomas Lundquist [this message]
2007-07-22  7:08       ` Ulf Samuelsson
2007-07-22 14:51         ` Thomas Lundquist
2007-07-22 15:03           ` Ulf Samuelsson

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=20070721184252.GA2523@zelow.no \
    --to=lists@zelow.no \
    --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