From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: new manifest format readers?
Date: Fri, 09 Jun 2017 15:56:45 +0200 [thread overview]
Message-ID: <87zidhl0wy.fsf@gnu.org> (raw)
In-Reply-To: <87zidhcqr9.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 09 Jun 2017 14:03:22 +0200")
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> Can we simplify this case by adding manifest readers for different
> formats? One simple format could be plain text:
>
> # this is for compilers
> gfortran@5
> gcc-toolchain@5
>
> # this is for fun
> cdogs-sdl
>
> The manifest reader would just discard # comments and interpret each
> non-empty line as a spec string.
Sounds reasonable.
I guess we’d need to add a new option to read this format, or should
‘guix package -m’ try to automatically dispatch based on the file name
extension with a new --format option to override the guess?
> While I love Scheme, I don’t think anything is to be gained from
> exposing users who don’t want to use Scheme for manifests to opaque
> blobs of code and syntax they don’t want to understand.
I thought everyone needed their dose of parentheses, but maybe you’re
right. :-)
Ludo’.
next prev parent reply other threads:[~2017-06-09 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 12:03 new manifest format readers? Ricardo Wurmus
2017-06-09 13:09 ` Mathieu Othacehe
2017-06-09 13:56 ` Ludovic Courtès [this message]
2017-06-09 13:58 ` Jan Nieuwenhuizen
2017-06-09 14:58 ` Ricardo Wurmus
2017-06-10 2:06 ` Arun Isaac
2017-06-11 14:15 ` Ludovic Courtès
2017-06-11 15:44 ` Ricardo Wurmus
2017-06-11 21:16 ` Ludovic Courtès
2017-06-12 3:56 ` Jan Nieuwenhuizen
2017-06-12 8:31 ` Chris Marusich
2017-06-09 15:08 ` Björn Höfling
2017-06-09 18:12 ` Ricardo Wurmus
2017-06-10 17:19 ` myglc2
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=87zidhl0wy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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 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).