From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: package patching
Date: Tue, 15 Nov 2011 19:14:38 +0000 [thread overview]
Message-ID: <201111151914.38517.arnout@mind.be> (raw)
In-Reply-To: <87k471n59k.fsf@macbook.be.48ers.dk>
On Tuesday 15 November 2011 08:45:11 Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas De Schampheleire
<patrickdepinguin+buildroot@gmail.com> writes:
> Hi,
>
> Thomas> I think we should try and improve this.
>
> Thomas> A first approach could be to simply remove support for
> Thomas> foo-1.2.3-something.patch, and require version-specific patches to
> be Thomas> in a versioned subdirectory, package/foo/foo-1.2.3. For this,
> we Thomas> should remove line 02-04. In this case, common patches are
> applied Thomas> first, followed by versioned patches in subdirectories.
>
> Yes, I know - We hit this with E.G. busybox in the past. I would go for
> the versioned-patches-in-subdir, as we (luckily) only support multiple
> versions for a limited number of packages.
While we're at it, I would also make it policy to not include the version
number in the patch, except for packages with multiple active versions. Now,
when you're upgrading a package, you also have to do a lot of renames of
patches.
Note that this fix will require renames of rougly 300 files...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-11-15 19:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 8:33 [Buildroot] RFC: package patching Thomas De Schampheleire
2011-11-15 8:45 ` Peter Korsgaard
2011-11-15 19:14 ` Arnout Vandecappelle [this message]
2011-11-15 21:28 ` Thomas Petazzoni
2011-11-16 6:18 ` Sergey Naumov
2011-11-16 6:50 ` Thomas De Schampheleire
2011-11-16 6:44 ` Thomas De Schampheleire
2011-11-16 18:03 ` Thomas Petazzoni
2011-11-17 13:05 ` Thomas De Schampheleire
2011-11-17 21:23 ` Arnout Vandecappelle
2011-11-17 21:42 ` Thomas Petazzoni
2011-11-18 6:53 ` Thomas De Schampheleire
2011-11-18 7:05 ` Thomas Petazzoni
2011-11-18 7:34 ` Peter Korsgaard
2011-11-18 9:26 ` Thomas De Schampheleire
2011-11-18 12:24 ` Michael S. Zick
2011-11-18 19:44 ` Arnout Vandecappelle
2011-11-18 19:27 ` Arnout Vandecappelle
2011-11-19 9:26 ` Bjørn Forsman
2011-11-19 12:13 ` Arnout Vandecappelle
2011-11-18 16:41 ` Thomas Petazzoni
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=201111151914.38517.arnout@mind.be \
--to=arnout@mind.be \
--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