Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] What would it take to add LZIP support for package downloads?
Date: Tue, 08 Sep 2015 12:14:22 -0500	[thread overview]
Message-ID: <55EF176E.4050001@ou.edu> (raw)

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?

Steve Kenton

             reply	other threads:[~2015-09-08 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 17:14 Steve Kenton [this message]
2015-09-08 20:24 ` [Buildroot] What would it take to add LZIP support for package downloads? 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=55EF176E.4050001@ou.edu \
    --to=skenton@ou.edu \
    --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