Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 for-2012.11 2/5] manual: various fixes
Date: Tue, 27 Nov 2012 22:58:01 +0100	[thread overview]
Message-ID: <50B53769.8080504@mind.be> (raw)
In-Reply-To: <CAHXCMMJqkV-M2k8d9Xo1v1YQ8E5oEQobpJHUrSbg=6fUWi4pmQ@mail.gmail.com>

On 27/11/12 22:04, Samuel Martin wrote:
>> >    * +LIBFOO_PATCH+ may contain the name of a patch, that will be
>> >      downloaded from the same location as the tarball indicated in
>> >      +LIBFOO_SOURCE+. If +HOST_LIBFOO_PATCH+ is not specified, it
>> >  -  defaults to +LIBFOO_PATCH+. Also note that another mechanism is
>> >  -  available to patch a package: all files of the form
>> >  -  +packagename-packageversion-description.patch+ present in the
>> >  +  defaults to +LIBFOO_PATCH+. Note that patches that are included
>> >  +  in Buildroot itself use a different mechanism: all files of the
>> >  +  form +packagename-packageversion-description.patch+ present in the
> Well, actually the pattern is "packagename-*.patch" in the following
> directories:
> - package/<packagename>/<packagename-packageversion>/ if this
> subdirectory exists;
> - package/<packagename>/ otherwise.

  I think mentioning those two directories goes a bit too far, but I'll
correct the pattern.


  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:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-11-27 21:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 20:02 [Buildroot] [PATCHv2 for-2012.11 1/5] manual: trivial fixes Arnout Vandecappelle
2012-11-27 20:02 ` [Buildroot] [PATCHv2 for-2012.11 2/5] manual: various fixes Arnout Vandecappelle
2012-11-27 21:04   ` Samuel Martin
2012-11-27 21:58     ` Arnout Vandecappelle [this message]
2012-11-27 20:02 ` [Buildroot] [PATCHv2 for-2012.11 3/5] manual: more warnings to not use output/target Arnout Vandecappelle
2012-11-27 21:04   ` Samuel Martin
2012-11-27 20:02 ` [Buildroot] [PATCHv2 for-2012.11 4/5] manual: give example where _INSTALL_TARGET = NO Arnout Vandecappelle
2012-11-27 21:04   ` Samuel Martin
2012-11-27 20:02 ` [Buildroot] [PATCHv2 for-2012.11 5/5] manual: restructure 'Adding packages' chapter Arnout Vandecappelle
2012-11-27 21:04   ` Samuel Martin
2012-11-27 21:04 ` [Buildroot] [PATCHv2 for-2012.11 1/5] manual: trivial fixes Samuel Martin
2012-11-27 21:18   ` Arnout Vandecappelle
2012-11-27 21:28     ` Samuel Martin
2012-11-27 21:30       ` Arnout Vandecappelle

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=50B53769.8080504@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