Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] Docu: Add LIBFOO_EXTRACT_CMDS
Date: Tue,  6 Aug 2013 23:36:20 +0200	[thread overview]
Message-ID: <1375824984-8226-2-git-send-email-s.martin49@gmail.com> (raw)
In-Reply-To: <1375824984-8226-1-git-send-email-s.martin49@gmail.com>

From: Stephan Hoffmann <sho@relinux.de>

[Samuel: add precision about non-tar archive]
Signed-off-by: Stephan Hoffmann <sho@relinux.de>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
---
 docs/manual/adding-packages-generic.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
index faf70b1..a6f9565 100644
--- a/docs/manual/adding-packages-generic.txt
+++ b/docs/manual/adding-packages-generic.txt
@@ -358,6 +358,10 @@ LIBFOO_VERSION = 2.32
 Now, the variables that define what should be performed at the
 different steps of the build process.
 
+* +LIBFOO_EXTRACT_CMDS+ lists the actions to be performed to
+  extract the package in case no standard method applies
+  (ie. non-tar archive).
+
 * +LIBFOO_CONFIGURE_CMDS+ lists the actions to be performed to
   configure the package before its compilation.
 
-- 
1.8.3.4

  reply	other threads:[~2013-08-06 21:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06 21:36 [Buildroot] [PATCH 0/5] Manual updates Samuel Martin
2013-08-06 21:36 ` Samuel Martin [this message]
2013-08-06 21:36 ` [Buildroot] [PATCH 2/5] manual: add patch revision and versioning section Samuel Martin
2013-08-06 22:18   ` Thomas Petazzoni
2013-08-07 17:41     ` Samuel Martin
2013-08-07 17:53       ` Thomas De Schampheleire
2013-08-07  5:40   ` Thomas De Schampheleire
2013-08-07 17:41     ` Samuel Martin
2013-08-06 21:36 ` [Buildroot] [PATCH 3/5] manual: update beyond Buildroot section Samuel Martin
2013-08-07  6:15   ` Thomas De Schampheleire
2013-08-07  9:39   ` Thomas Petazzoni
     [not found]     ` <CAKvQZ_3UxzreEtWQ3E++3xZ1o4W_Rn1gzKrYQo2CNOnQ_hZpfg@mail.gmail.com>
2013-08-08 12:36       ` Samuel Martin
2013-08-08 18:01         ` Thomas Petazzoni
2013-08-13  5:59           ` Arnout Vandecappelle
2013-08-15 19:01             ` Samuel Martin
2013-08-22 18:03               ` Arnout Vandecappelle
2013-09-25 20:31                 ` Thomas De Schampheleire
2013-08-06 21:36 ` [Buildroot] [PATCH 4/5] manual: add tips to build manual Samuel Martin
2013-08-07  6:18   ` Thomas De Schampheleire
2013-08-06 21:36 ` [Buildroot] [PATCH 5/5] manual: minor formating fixes Samuel Martin
2013-08-07  6:16   ` Thomas De Schampheleire

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=1375824984-8226-2-git-send-email-s.martin49@gmail.com \
    --to=s.martin49@gmail.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