From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Easy Upgrade Path?
Date: Tue, 10 Feb 2009 10:00:32 +0100 [thread overview]
Message-ID: <87d4dq7jkf.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <d6cda7730902091413h5e7cbd21ra41d7154ca60909e@mail.gmail.com> ("Thiago A. Corrêa"'s message of "Mon\, 9 Feb 2009 20\:13\:37 -0200")
>>>>> "Thiago" == Thiago A Corr?a <thiago.correa@gmail.com> 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?
Thiago> I don't know if there is any recommended way. None is
Thiago> documented, and I guess each one does whatever they see best.
Thiago> I had the same problem as you, and after some thought I
Thiago> decided the best approach would be to "fork" from buildroot
Thiago> svn to my own private svn server (svn export) and do my
Thiago> changes there. I've also added a file upstream.rev which only
Thiago> contains the last revision from svn that I have merged from
Thiago> upstream (svn diff -r last:current > upstream-rev.patch &&
Thiago> patch -p0 < upstream-rev.patch).
There's an easier way - Take a look@vendor branches and the
svn_load_dirs.pl in the svn book.
Thiago> Also, generic changes/development, I try to push upstream
Thiago> whenever possible. This both benefits other users and also
Thiago> helps us keeping the differences smaller, so merges with
Thiago> upstream are a bit easier.
Exactly.
Thiago> This is far from a good solution, but has worked so far.
We do something similar (using vendor branches though), and it works
pretty well. We might want to do something to make it easier to keep
the project/device specific stuff seperate though.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-02-10 9:00 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 [this message]
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
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=87d4dq7jkf.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox