unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 38256@debbugs.gnu.org
Subject: bug#38256: Packages sources in '.tar.lz' archives
Date: Sat, 23 Nov 2019 18:37:20 +0100	[thread overview]
Message-ID: <87lfs6335b.fsf@gnu.org> (raw)
In-Reply-To: <878sodqpmf.fsf@yamatai> (Guillaume Le Vaillant's message of "Mon, 18 Nov 2019 14:29:44 +0100")

Hi Guillaume,

Guillaume Le Vaillant <glv@posteo.net> skribis:

> Currently, when package sources are in a '.tar.lz' archive (e.g. ed,
> wget, ddrescue, etc.), the 'lzip' package must be explicitly put into
> the 'native-inputs' of the package definition, or building the package
> fails.
>
> Would it be possible to make the 'lzip' package available by default in
> the build process, like 'gzip', 'bzip2' and 'xz'?

Yes.  There’s not a strong incentive because there are relatively few
packages distributed as lz files, but we could do that in
‘core-updates’.

Thanks,
Ludo’.

      reply	other threads:[~2019-11-23 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18 13:29 bug#38256: Packages sources in '.tar.lz' archives Guillaume Le Vaillant
2019-11-23 17:37 ` Ludovic Courtès [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lfs6335b.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38256@debbugs.gnu.org \
    --cc=glv@posteo.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).