unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: jgart <jgart@dismail.de>, 60630@debbugs.gnu.org
Subject: [bug#60630] [PATCH] guix: channels: Add description field.
Date: Mon, 09 Jan 2023 17:25:35 +0100	[thread overview]
Message-ID: <874jszsmio.fsf_-_@gnu.org> (raw)
In-Reply-To: <275d6e457ade39fc591062a6274ebaf2960d1b5d.camel@gmail.com> (Liliana Marie Prikler's message of "Sun, 08 Jan 2023 16:43:45 +0100")

Hi,

Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:

> Am Samstag, dem 07.01.2023 um 10:24 -0600 schrieb jgart:
>> * guix/channels.scm (<channel>): Add channel description field and
>> comment disambiguating the type expected in an introduction field.
>> * doc/guix.scm (Invoking guix describe): Add channel description
>> field to channels record instance example.
>> 
>> This commit adds an optional description field to a channel intended
>> to describe the channel. Its purpose is similar to the description
>> field in a <package> record.
> Since channel descriptions would be maintained by the user and neither
> Guix' nor the channel's authors, I think it's safe to say that this
> description field would in effect be nothing more but a comment. 

Right, I agree.  What use case did you have in mind, jgart?

Most likely, a description could go to the ‘.guix-channel’ file, if it’s
of any use.

Thanks,
Ludo’.




  reply	other threads:[~2023-01-09 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 16:24 [bug#60630] [PATCH] guix: channels: Add description field jgart via Guix-patches via
2023-01-08 15:43 ` Liliana Marie Prikler
2023-01-09 16:25   ` Ludovic Courtès [this message]
2023-01-10  2:38   ` jgart via Guix-patches via
2023-01-10  9:50     ` 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=874jszsmio.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=60630@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=liliana.prikler@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).