unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 34807@debbugs.gnu.org
Subject: [bug#34807] [PATCH 1/2] Add (guix lzlib).
Date: Sat, 04 May 2019 23:09:40 +0200	[thread overview]
Message-ID: <87ef5e0vvv.fsf@gnu.org> (raw)
In-Reply-To: <878svm5xic.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sat, 04 May 2019 12:23:23 +0200")

Hello!

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Right on time, I just finished it!
>
> - I've been in touch with Antonio, Lzip's maintainer, for more than a
>   week and now I'm confident that I have a decent understanding of the
>   library.
>
> - Your m4 suggestion didn't work.  I've included a comment.  We need to
>   fix it before merging.  I'm not the right person for this job I'm
>   afraid :p  Ludo?

Sure, I can do it.

> - The convenience functions do not support multi-member archives.
>   Multi-member archives are mostly useful for parallelization, but we
>   don't use that in Guix, so it's OK.  Should it be required some day,
>   we would need to implement it, which requires a little bit more work.
>   I've documented all that.
>
> - The implementation of lzread! is subpar because I understood a
>   subtlety a bit too late.  But that's alright, it does not affect
>   performance nor reliability.
>
> - I've included 11 tests covering all your suggestions.
>
> - I haven't strace'd the Guile process.  The code regarding ports is
>   identical to zlib.scm, so it's unlikely there would be an issue in
>   this area.  I have never done this before, so out of curiosity, how do
>   you run a specific Guix tests without going through `make'?
>
> Next steps? :D

This looks all good to me!

I was about to apply it and add the Autoconf machinery, but I thought we
could also make it a separate project that could be beneficial to other
Guilers out there (like we did with Guile-Gcrypt and Guile-Git).
Incidentally that would also avoid the need for adding the ‘%liblz’
variable in (guix config), which simplifies things a bit.

WDYT?

If you want to take that route, I’m happy to help with the Autotools
machinery (or you could use ‘hall’ from the ‘guile-hall’ package to do
that for you.)

If you don’t feel like taking that route (or at least not yet ;-)),
that’s OK for me too, I don’t feel strongly either way.

Thoughts?

Thank you!

Ludo’.

  reply	other threads:[~2019-05-04 21:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 18:02 [bug#34807] [PATCH 1/2] Add (guix lzlib) Pierre Neidhardt
2019-03-10 18:09 ` [bug#34807] [PATCH 2/2] dir-locals.el: Add 'call-with-lzip-input-port' and 'call-with-lzip-output-port' keywords Pierre Neidhardt
2019-03-22 21:35 ` [bug#34807] [PATCH 1/2] Add (guix lzlib) Ludovic Courtès
2019-05-01 16:46   ` Pierre Neidhardt
2019-05-02  9:16     ` Pierre Neidhardt
2019-05-04  9:11       ` Ludovic Courtès
2019-05-04 10:23         ` Pierre Neidhardt
2019-05-04 21:09           ` Ludovic Courtès [this message]
2019-05-04 21:39             ` Pierre Neidhardt
2019-05-06 21:18               ` Ludovic Courtès
2019-05-06 23:28                 ` Tobias Geerinckx-Rice
2019-05-07  7:02                   ` Pierre Neidhardt
2019-05-07 15:44                     ` bug#34807: " Ludovic Courtès
2019-05-07 15:51                       ` [bug#34807] " Pierre Neidhardt
2019-05-07  8:19                   ` Ludovic Courtès

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=87ef5e0vvv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34807@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).