From: Christopher Baines <mail@cbaines.net>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: guix-devel@gnu.org
Subject: Re: #f as a package description, gnu: Add rocminfo.
Date: Mon, 09 Aug 2021 22:44:23 +0100 [thread overview]
Message-ID: <87tujyi98o.fsf@cbaines.net> (raw)
In-Reply-To: <YRDXiEhcMm5zLJYO@noor.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Lars-Dominik Braun <lars@6xq.net> writes:
> Hi Christopher,
>
>> Anyway, I wouldn't like for this change to lower the standard though,
>> it's currently the only package in Guix with an invalid description (as
>> far as I'm aware), is there some reason why it doesn't have one?
> it simply fell through the cracks[1]. Commit
> 0a379de3249d5e9ff66fb404f7e5aa8ce2cb3d24 adds a proper descripton.
>
> Sorry for the trouble,
No problem, thanks for fixing it.
> [1] Unfortunately I cannot run `guix lint` on an entire git changeset,
> so instead I have to check each package by hand and I probably missed
> rocminfo. I wish someday we can have a branch/pull-request-based
> workflow with automated CI checks (linting, `guix pull`, signature
> verification, …) *before* merging to master.
This is something I've put some time in to, but it needs some general
support before I'm confident that the things I have in mind can become
reality. I recently started a thread on guix-devel [1] about what I have
in mind, so please comment if you're interested in this area.
1: https://lists.gnu.org/archive/html/guix-devel/2021-08/msg00001.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2021-08-09 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210808145723.7941.35341@vcs0.savannah.gnu.org>
[not found] ` <20210808145729.2F8D620BD3@vcs0.savannah.gnu.org>
2021-08-08 20:33 ` #f as a package description, gnu: Add rocminfo Christopher Baines
2021-08-09 7:21 ` Lars-Dominik Braun
2021-08-09 21:44 ` Christopher Baines [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tujyi98o.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=lars@6xq.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.