Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Docu: Add LIBFOO_EXTRACT_CMDS
Date: Sat, 16 Feb 2013 17:22:53 +0100	[thread overview]
Message-ID: <511FB25D.3040408@relinux.de> (raw)
In-Reply-To: <510806E9.9060504@mind.be>

Am 29.01.2013 18:29, schrieb Arnout Vandecappelle:
> On 29/01/13 11:39, Stephan Hoffmann wrote:
>> Am 29.01.2013 11:18, schrieb Samuel Martin:
> [snip]
>>>> >>+* +LIBFOO_EXTRACT_CMDS+ lists the actions to be performed to
>>>> >>+  extract the package in case no standard method applies
>>> >It could be nice to add what are the standard/supported methods
>> Sure. But I do not know them, I just decided to document this one
>> because I had to search for the information recently.
>
>  There is currently only one: tar - and if you don't override the
> commands, tar is used regardless of filetype or extension.
>
>  It supports three compression types: gzip (extension .gz or .tgz),
> bzip2 (extension .bz2, .tbz or .tbz2), and xz (extension .xz).
>
>  Feel free to copy the above directly :-)
>
I do not think that the list of XXX_CMDS variables is the right place to
document the default behavior without them.

Of course whe should have a documentation of the default behaior
somewhere in the manual, but I am not enough familiar with this topic to
write it.

So I suggest to commit my patch as it is, it still applies to HEAD.

Regards

Stephan
>  Regards,
>  Arnout
>
>


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

  reply	other threads:[~2013-02-16 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 10:04 [Buildroot] [PATCH] Docu: Add LIBFOO_EXTRACT_CMDS Stephan Hoffmann
2013-01-29 10:18 ` Samuel Martin
2013-01-29 10:39   ` Stephan Hoffmann
2013-01-29 17:29     ` Arnout Vandecappelle
2013-02-16 16:22       ` Stephan Hoffmann [this message]
2013-02-16 17:35         ` 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=511FB25D.3040408@relinux.de \
    --to=sho@relinux.de \
    --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