Packages sources in '.tar.lz' archives

  • Open
  • quality assurance status badge
Details
2 participants
  • Guillaume Le Vaillant
  • Ludovic Courtès
Owner
unassigned
Submitted by
Guillaume Le Vaillant
Severity
normal
G
G
Guillaume Le Vaillant wrote on 18 Nov 2019 14:29
(address . bug-guix@gnu.org)
878sodqpmf.fsf@yamatai
Hi,

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'?
L
L
Ludovic Courtès wrote on 23 Nov 2019 18:37
(name . Guillaume Le Vaillant)(address . glv@posteo.net)(address . 38256@debbugs.gnu.org)
87lfs6335b.fsf@gnu.org
Hi Guillaume,

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

Toggle quote (8 lines)
> 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’.
?