From: "Ludovic Courtès" <ludo@gnu.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 40246@debbugs.gnu.org
Subject: [bug#40246] [PATCH] gnu: Add cramfs-tools.
Date: Wed, 01 Apr 2020 23:22:46 +0200 [thread overview]
Message-ID: <87sghmsxy1.fsf@gnu.org> (raw)
In-Reply-To: <CAEwRq=r09qqcCfgC=CpMJZ4g3JztS8SkDieSHMPpMjpOH39QyA@mail.gmail.com> (Vincent Legoll's message of "Thu, 26 Mar 2020 23:34:03 +0100")
Hi Vincent,
Vincent Legoll <vincent.legoll@gmail.com> skribis:
> From ff79a4b2d798bba222ac502a7aa1f7ef0a97e249 Mon Sep 17 00:00:00 2001
> From: Vincent Legoll <vincent.legoll@gmail.com>
> Date: Thu, 26 Mar 2020 23:12:53 +0100
> Subject: [PATCH] gnu: Add cramfs-tools.
>
> * gnu/packages/linux.scm (cramfs-tools): New variable.
[...]
> + (name "cramfs-tools")
> + (version "2.1")
> + (source (origin
> + (method url-fetch)
> + (uri (string-append
> + "https://github.com/npitre/cramfs-tools/archive/v"
As reported by ‘guix lint’, please don’t refer to a generated tarball.
Instead you can use a hosted “hand-crafted” tarball if there’s one or,
more likely, ‘git-fetch’.
> + (synopsis "Tools to manage Cramfs filesystems")
> + (description "Cramfs is a Linux filesystem designed to be simple, small,
> +and to compress things well. It is used on a number of embedded systems and
> +small devices. This version has additional features such as uncompressed
> +blocks and random block placement.")
Could you write “file systems” (two words)? This is by convention in
GNU and Guix.
Thanks in advance!
Ludo’.
next prev parent reply other threads:[~2020-04-01 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 22:34 [bug#40246] [PATCH] gnu: Add cramfs-tools Vincent Legoll
2020-03-26 23:22 ` [bug#40246] " Vincent Legoll
2020-04-01 21:22 ` Ludovic Courtès [this message]
2020-04-01 21:46 ` [bug#40246] [PATCH] " Vincent Legoll
2020-04-02 8:01 ` bug#40246: " Ludovic Courtès
2020-04-02 8:03 ` [bug#40246] " Vincent Legoll
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=87sghmsxy1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40246@debbugs.gnu.org \
--cc=vincent.legoll@gmail.com \
/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).