From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Easy Upgrade Path?
Date: Fri, 13 Feb 2009 11:10:00 +1100 [thread overview]
Message-ID: <20090213001000.GA22653@cloud.net.au> (raw)
In-Reply-To: <20090212132945.GA30222@zelow.no>
On Thu, Feb 12, 2009 at 02:29:45PM +0100, Thomas Lundquist wrote:
> On Mon, Feb 09, 2009 at 10:53:34AM -0800, Dan Pattison wrote:
> >
> > Hello List:
> >
> > I've been getting used to the buildroot development environment using
> > 2009.02-RC2 for ARM AT91SAM9g20-EK. I have made lots of changes and
> > additions that suit our project (config files, packages, etc.) We have
> > successfully compiled and included some of our own programs.
> >
> > What is the recommended method to upgrade to the newest build
> > environment so we don't have to re-do everything? Is this possible?
>
> Ulf introduced local/ when he started to commit and this was a good idea.
>
> It got booted out some time later, by someone.
>
> The point is that you can put your config files and non-included
> packages there and keep that out of the rest of the tree.
>
> I like the idea and would like to put it back in.
I'm using local/ a lot in my own development. I have config files
(buildroot, busybox, linux, uClibc), the device table and the
target_skeleton in there.
There wasn't any support for additional packages via local/ although it
would be useful - I had to modify the top level makefiles to add such a
section here, making maintenance more difficult.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2009-02-13 0:10 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
2009-02-12 18:05 ` Ulf Samuelsson
2009-02-14 16:52 ` Thomas Lundquist
2009-02-13 0:10 ` Hamish Moffatt [this message]
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=20090213001000.GA22653@cloud.net.au \
--to=hamish@cloud.net.au \
--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.