All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Easy Upgrade Path?
Date: Thu, 12 Feb 2009 14:35:18 +0100	[thread overview]
Message-ID: <87k57vg4mh.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090212132945.GA30222@zelow.no> (Thomas Lundquist's message of "Thu\, 12 Feb 2009 14\:29\:45 +0100")

>>>>> "Thomas" == Thomas Lundquist <lists@zelow.no> writes:

Hi,

 >> What is the recommended method to upgrade to the newest build 
 >> environment so we don't have to re-do everything? Is this possible?

 Thomas> Ulf introduced local/ when he started to commit and this was
 Thomas> a good idea.

 Thomas> It got booted out some time later, by someone.

I don't remember the details, but it was afaik quite half baked,

 Thomas> The point is that you can put your config files and non-included 
 Thomas> packages there and keep that out of the rest of the tree.

 Thomas> I like the idea and would like to put it back in.

I agree that we should realize the fact that any big user of buildroot
want to customize it somehow and make it easy to do - But we need to
do it in a clean way.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-02-12 13:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 18:53 [Buildroot] Easy Upgrade Path? Dan Pattison
2009-02-09 22:13 ` Thiago A. Corrêa
2009-02-10  9:00   ` Peter Korsgaard
2009-02-11  1:35   ` Dan Pattison
2009-02-17 20:56     ` Thiago A. Corrêa
2009-02-19 15:34       ` Peter Korsgaard
2009-02-12 13:29 ` Thomas Lundquist
2009-02-12 13:35   ` Peter Korsgaard [this message]
2009-02-12 18:05     ` Ulf Samuelsson
2009-02-14 16:52     ` Thomas Lundquist
2009-02-13  0:10   ` Hamish Moffatt
2009-02-13  2:05     ` Eric Malkowski

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=87k57vg4mh.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.