From: David Pirotte <david@altosw.be>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: Release!
Date: Sat, 7 Oct 2017 09:21:31 -0300 [thread overview]
Message-ID: <20171007092131.650aaaae@capac> (raw)
In-Reply-To: <ce7885ac-ed28-c176-8c54-e7c25ec32451@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
Hello Hartmut,
> > so why would we 'abandon' s-exp, what would we win here?
> It might be interesting to *create* these files using tools written in
> other programming languages. And modules for creating *JSON* are
> available for most programming languages.
But that would be another tool, another package manager, not potluck... written by
we don't know who, neither when ... and that would be a totally separate effort,
that would not contribute to potluck ... which needs help (I wish I had the time...)
Potluck package definitions are generated, adjusted 'by hand' - mostly to update
the description, sometimes the copyright - then that is used to generated a Guix
package, which is a Guile scheme module: It makes no sense to me that the
potluck package representation would be anything but s-expr:
actually, most guilers do the exact opposite :) - when an app or a lib
either produces or needs xml, html, json ... the first thing they do is to
transform these into s-expr, so these become (a lot more) readable and
hackable ...
> (OTOH TOML[]1] could be a better format than JSON – it's much like
> .ini-files, but more formal specification...
Absolutely terrible :):) I hope we never do that, at least not for the 'official'
and maintained potluck package representation.
Again, my 2c.
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-10-07 12:21 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 13:11 What’s next? Ludovic Courtès
2017-05-24 13:23 ` Ricardo Wurmus
2017-05-27 10:01 ` Ludovic Courtès
2017-05-27 21:44 ` Ricardo Wurmus
2017-05-28 20:44 ` Ludovic Courtès
2017-05-28 21:36 ` Ricardo Wurmus
2017-05-30 15:55 ` Ludovic Courtès
2017-05-24 15:52 ` Brendan Tildesley
2017-05-27 10:04 ` Ludovic Courtès
2017-05-28 20:41 ` Maxim Cournoyer
2017-05-30 15:17 ` Ludovic Courtès
2017-06-03 21:16 ` Maxim Cournoyer
2017-05-24 16:09 ` Catonano
2017-05-24 16:25 ` Jan Nieuwenhuizen
2017-05-24 18:40 ` Adonay Felipe Nogueira
2017-05-24 19:34 ` Catonano
2017-05-24 19:56 ` Ricardo Wurmus
2017-05-30 0:09 ` myglc2
2017-05-24 21:47 ` Leo Famulari
2017-05-24 21:45 ` Leo Famulari
2017-05-25 8:11 ` What???s next? Pjotr Prins
2017-05-27 10:16 ` Ludovic Courtès
2017-05-28 7:30 ` What's next? Pjotr Prins
2017-05-28 20:48 ` Ludovic Courtès
2017-05-28 22:05 ` Roel Janssen
2017-05-30 15:19 ` Ludovic Courtès
2017-05-30 20:15 ` Pjotr Prins
2017-05-29 2:31 ` Maxim Cournoyer
2017-05-28 20:37 ` What???s next? Maxim Cournoyer
2017-05-28 21:34 ` Ricardo Wurmus
2017-05-30 15:14 ` Ludovic Courtès
2017-05-25 14:57 ` What’s next? Chris Marusich
2017-05-25 18:32 ` Leo Famulari
2017-05-25 20:01 ` Ricardo Wurmus
2017-05-25 20:41 ` Adonay Felipe Nogueira
2017-05-27 10:13 ` Ludovic Courtès
2017-05-29 23:28 ` myglc2
2017-06-08 14:35 ` Ricardo Wurmus
2017-05-27 10:09 ` Ludovic Courtès
2017-10-04 15:12 ` Release! Ludovic Courtès
2017-10-05 19:18 ` Release! Christopher Baines
2017-10-06 13:01 ` Release! Ludovic Courtès
2017-10-09 7:25 ` Release! Christopher Baines
2017-10-09 16:25 ` Release! Ludovic Courtès
2017-10-06 18:30 ` Release! Ricardo Wurmus
2017-10-06 23:31 ` Release! David Pirotte
2017-10-07 9:18 ` Release! Hartmut Goebel
2017-10-07 12:21 ` David Pirotte [this message]
2017-10-07 21:30 ` Release! Ricardo Wurmus
2017-10-08 13:08 ` Release! Hartmut Goebel
2017-10-07 4:06 ` [PATCH] DRAFT: build: Compile scheme modules in batches (was Re: Release!) Mark H Weaver
2017-10-07 19:35 ` Efraim Flashner
2017-10-08 9:19 ` Ricardo Wurmus
2017-10-08 12:03 ` Ricardo Wurmus
2017-10-08 13:26 ` Ricardo Wurmus
2017-10-09 7:38 ` Ludovic Courtès
2017-10-09 11:32 ` Ricardo Wurmus
2017-10-10 6:52 ` Ricardo Wurmus
2017-10-09 7:42 ` Ludovic Courtès
2017-10-09 7:53 ` Release! Ludovic Courtès
2017-11-20 22:07 ` Release! Ludovic Courtès
2017-11-30 10:40 ` Release! Ludovic Courtès
2017-12-01 2:57 ` Release! Maxim Cournoyer
2017-12-01 18:30 ` Release! Leo Famulari
2017-12-01 19:32 ` Release! Ricardo Wurmus
2017-12-04 8:53 ` Release! Ludovic Courtès
2017-12-04 8:58 ` ISO image available for testing! Ludovic Courtès
2017-12-04 21:35 ` Christopher Baines
2017-12-04 22:34 ` Ludovic Courtès
2017-12-05 22:47 ` Ludovic Courtès
2017-12-06 0:52 ` Mark H Weaver
2017-12-06 1:17 ` Ben Woodcroft
2017-12-06 2:16 ` native-inputs ending up as run-time references [was: ISO image available for testing!] Tobias Geerinckx-Rice
2017-12-06 3:18 ` Leo Famulari
2017-12-06 3:48 ` Tobias Geerinckx-Rice
2017-12-06 8:04 ` ISO image available for testing! Mark H Weaver
2017-12-06 8:14 ` Ludovic Courtès
2017-12-06 16:29 ` Tobias Geerinckx-Rice
2017-12-07 20:09 ` Christopher Baines
2017-12-07 21:19 ` Ludovic Courtès
2017-12-04 8:52 ` Release! Ludovic Courtès
2017-12-05 2:47 ` Release! Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2022-06-03 16:41 Release v1.4? Ludovic Courtès
2022-06-06 21:17 ` Merging ‘staging’? Ludovic Courtès
2022-06-08 11:50 ` Efraim Flashner
2022-06-08 21:24 ` Ludovic Courtès
2022-06-10 7:57 ` Efraim Flashner
2022-06-11 9:53 ` Ludovic Courtès
2022-06-12 3:58 ` Efraim Flashner
2022-06-12 21:08 ` Ludovic Courtès
2022-06-13 7:03 ` Ludovic Courtès
2022-06-14 10:32 ` Release ? (was: Merging ‘staging’?) zimoun
2022-06-14 13:08 ` Efraim Flashner
2022-06-15 9:21 ` Release ? 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171007092131.650aaaae@capac \
--to=david@altosw.be \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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 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.