From: Daniel Laird <daniel.j.laird@nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot] Makefile.autotools.in problems
Date: Thu, 10 Jul 2008 00:37:28 -0700 (PDT) [thread overview]
Message-ID: <18377517.post@talk.nabble.com> (raw)
I have a problem with the Makefile.autotools.in when it does the patch
target.
The target creates a NAMEVER string (pkg_name-version). It then checks to
see if it has any version specific files. i.e pango-1.19.3.*.patch.
If it has is applies them and exits. (appies no generic patches)
The problem is that if I bounce the version to 1.22.0. It does the check
and decides there are no version specific patches. It then applies all
patches in the directory regardless.
This is only a problem as I have not deleted patches associated with an old
version.
However I wanted to raise the issue in case it was originally planned that
you could have multiple patches in the directory for different versions and
it would apply only those patches that match.
Perhaps we could have a PKG_STRICT_PATCH variable. That if set to true
would only apply patches that match the version string, if not set it would
apply all patches.
Any ideas, opinions?
Cheers
Dan
--
View this message in context: http://www.nabble.com/Makefile.autotools.in-problems-tp18377517p18377517.html
Sent from the BuildRoot mailing list archive at Nabble.com.
next reply other threads:[~2008-07-10 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 7:37 Daniel Laird [this message]
2008-07-10 7:47 ` [Buildroot] Makefile.autotools.in problems Peter Korsgaard
2008-07-10 13:31 ` Ulf Samuelsson
2008-07-11 8:02 ` Daniel Laird
2008-07-11 8:17 ` Bernhard Fischer
2008-07-11 8:56 ` Daniel Laird
2008-07-11 12:36 ` Daniel Laird
2008-07-11 12:42 ` Daniel Laird
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=18377517.post@talk.nabble.com \
--to=daniel.j.laird@nxp.com \
--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