From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/5] package: add generic support for lz archives
Date: Thu, 16 Feb 2017 09:34:05 +0100 [thread overview]
Message-ID: <20170216093405.24f25e54@free-electrons.com> (raw)
In-Reply-To: <19a785a4-beaf-92dd-c53b-6e81dde24c7d@mind.be>
Hello,
On Thu, 16 Feb 2017 09:25:55 +0100, Arnout Vandecappelle wrote:
> > BR2_LZCAT does not specify only the path to the lzcat program, but also
> > its options. And we completely ignore those custom options if the
> > lzcat built by Buildroot is used.
>
> It is possible to provide extra options, but these are completely useless.
> Well, actually, lzcat is the first one with an option that could be useful:
> --threads, to decompress over several cores. Except that --threads isn't
> implemented yet for decompression. So, although it is possible to add extra
> options in BR2_LZCAT, it just makes no sense.
My point is not whether it makes sense or not to be able to pass
options to lzip. My point is that we provide a Config.in option to
allow the user to pass additional options, but we don't actually take
into account the value of this option when we build our own host-lzip or
host-xz.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-16 8:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 20:15 [Buildroot] [PATCH v3 1/5] package: refactor listing of extractor dependencies Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 2/5] package: add generic support for lz archives Baruch Siach
2017-02-14 13:43 ` Thomas De Schampheleire
2017-02-15 21:15 ` Thomas Petazzoni
2017-02-15 22:48 ` Arnout Vandecappelle
2017-02-16 7:32 ` Thomas Petazzoni
2017-02-16 8:25 ` Arnout Vandecappelle
2017-02-16 8:34 ` Thomas Petazzoni [this message]
2017-02-16 17:24 ` Arnout Vandecappelle
2017-02-16 17:41 ` Yann E. MORIN
2017-02-16 22:03 ` Peter Korsgaard
2017-02-16 22:11 ` Yann E. MORIN
2017-02-17 7:43 ` Arnout Vandecappelle
2017-02-17 17:07 ` Yann E. MORIN
2017-02-16 22:08 ` Peter Korsgaard
2017-02-16 8:36 ` Thomas De Schampheleire
2017-02-16 8:40 ` Thomas Petazzoni
2017-02-16 10:24 ` Thomas De Schampheleire
2017-02-21 21:55 ` [Buildroot] Bug in "package: add generic support for lz archives" ? Thomas Petazzoni
2017-02-22 5:32 ` Baruch Siach
2017-02-22 8:03 ` Thomas Petazzoni
2017-02-12 20:15 ` [Buildroot] [PATCH v3 3/5] ed: use generic extract command Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 4/5] ddrescue: " Baruch Siach
2017-02-12 20:15 ` [Buildroot] [PATCH v3 5/5] ocrad: " Baruch Siach
2017-02-14 13:42 ` [Buildroot] [PATCH v3 1/5] package: refactor listing of extractor dependencies Thomas De Schampheleire
2017-02-14 21:39 ` Thomas Petazzoni
2017-02-15 7:04 ` Baruch Siach
2017-02-15 21:13 ` 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=20170216093405.24f25e54@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.