unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 62050@debbugs.gnu.org
Subject: [bug#62050] [PATCH] gnu: Add tissue.
Date: Fri, 17 Mar 2023 13:43:17 +0000	[thread overview]
Message-ID: <87lejvbiiy.fsf@systemreboot.net> (raw)
In-Reply-To: <87bkks9xi1.fsf@gnu.org>


Hi Ludo,

> Note that Disarchive does not support lzip (yet).
>
> Thus it’s be a bit more archival-friendly if you would instead either
> refer to a gzip tarball or refer to the Git repo.  It’s not a blocker
> though.

I really like lzip due to its supposedly better
design. https://www.nongnu.org/lzip/safety_of_the_lzip_format.html I've
been speaking to Timothy Sample about supporting lzip in
disarchive. It's a non-trivial amount of work, but I'll try to get it
done.

>> +     (list #:make-flags #~(list (string-append "prefix=" #$output))
>> +           #:modules `(((guix build guile-build-system)
>> +                        #:select (target-guile-effective-version))
>> +                       ,@%gnu-build-system-modules)
>
> You can change the last line to just (guix build gnu-build-system).

Replacing %gnu-build-system-modules with (guix build gnu-build-system)
does not work since we also need (guix build utils). I could replace
%gnu-build-system-modules with (guix build gnu-build-system) and (guix
build utils), but is there something wrong with using
%gnu-build-system-modules?

> Next step is a system service I guess?  :-)

Yep! I have a service in the guix-forge channel, but it uses a few
guix-forge specific constructs. I'll try and adapt it.

Regards,
Arun




  reply	other threads:[~2023-03-17 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 14:12 [bug#62050] [PATCH] gnu: Add tissue Arun Isaac
2023-03-16 21:50 ` Ludovic Courtès
2023-03-17 13:43   ` Arun Isaac [this message]
2023-03-17 21:43     ` Ludovic Courtès
2023-03-18 17:28       ` bug#62050: " Arun Isaac
2023-04-04 11:20     ` [bug#62050] " Simon Tournier

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=87lejvbiiy.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=62050@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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).