From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] What would it take to add LZIP support for package downloads?
Date: Tue, 8 Sep 2015 22:24:39 +0200 [thread overview]
Message-ID: <55EF4407.8040404@mind.be> (raw)
In-Reply-To: <55EF176E.4050001@ou.edu>
On 08-09-15 19:14, Steve Kenton wrote:
> I'm trying to set up a package for ddrescue
> https://www.gnu.org/software/ddrescue/
>
> and it's only available compressed with lzip (tar.lz)
> http://www.nongnu.org/lzip/lzip.html
>
> A manual trial run seems to indicate that it's not a supported format for downloaded packages
>
>>>> ddrescue 1.19 Extracting
> /ssd/bcdist/buildroot-2015.05/dl/ddrescue-1.19.tar.lz | tar --strip-components=1 -C /ssd/bcdist/buildroot-2015.05/output/build/ddrescue-1.19 -xf -
> /bin/bash: /ssd/bcdist/buildroot-2015.05/dl/ddrescue-1.19.tar.lz: Permission denied
> tar: This does not look like a tar archive
> tar: Exiting with failure status due to previous errors
>
> So, what would it take to add lzip support for downloaded packages?
> Easy or Oh My?
The simple solution is to extend the suitable-extractor function with .lz ->
lzip, and let dependencies.sh check that it's installed on the host. That's a
one-line change. But I don't think that many distros have lzip installed, so
it's a bit of a hassle for the user.
The intermediate solution is to make the ddrescue package depend on host-lzip
(which obviously you have to add as well), and define a custom extractor.
The full solution is to extend the DL_TOOLS_DEPENDENCIES handling with
dependencies on the host package rather than checks in dependencies.sh.
I propose you go for the simple solution :-)
Regards,
Arnout
>
> Steve Kenton
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-09-08 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 17:14 [Buildroot] What would it take to add LZIP support for package downloads? Steve Kenton
2015-09-08 20:24 ` Arnout Vandecappelle [this message]
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=55EF4407.8040404@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