From: Alex Kost <alezost@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>, David Craven <david@craven.ch>
Subject: Re: [PATCH] ui: 'package->recutils' serializes the source field.
Date: Fri, 12 Aug 2016 11:33:03 +0300 [thread overview]
Message-ID: <87lh02gzeo.fsf@gmail.com> (raw)
In-Reply-To: <87ziojb6kj.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 11 Aug 2016 18:42:36 +0200")
Ricardo Wurmus (2016-08-11 19:42 +0300) wrote:
> Alex Kost <alezost@gmail.com> writes:
>
>> David Craven (2016-08-10 17:13 +0300) wrote:
>>
>>>> Even so, if one insisted on using the recutils output in a programmatic
>>>> fashion (e.g. in a bash script), it would be best to run “guix build
>>>> --source” on the package names to obtain the actual source tarballs that
>>>> are used by Guix.
>>>
>>> I don't disagree. Alex what do you think?
>>
>> Do you mean about your original proposal? I am for it: I don't
>> comprehend why the source URL can't be displayed (especially since a
>> user can easily find it anyway), but I don't understand FSDG well enough
>> to judge, so I prefer not to participate in this discussion.
>
> I have previously stated that I’m not convinced that we really need a
> serialisation of the “source” field in the user-facing recutils output.
> The patch was a welcome demonstration of how this feature would look
> like.
Yes, I agree that it's a good demonstration of using Scheme API to get
any package info you need. But many (probably most) people do not know
Guile and this Guix package API well enough, and for them it may be much
easier to operate on the recutils output of "guix package --show" in
their scripts. If I understand correctly, that's why David suggested
that patch.
P.S. I don't want to raise another wave of messages in this thread :-)
If I understand it right, everyone agreed on not merging the patch.
--
Alex
next prev parent reply other threads:[~2016-08-12 14:15 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 20:49 How to get the package metadata as structured data? David Craven
2016-08-04 21:08 ` Ludovic Courtès
2016-08-04 22:03 ` Cook, Malcolm
2016-08-05 10:17 ` David Craven
2016-08-05 11:04 ` David Craven
2016-08-05 12:40 ` Aljosha Papsch
2016-08-05 14:50 ` Philippe Ombredanne
2016-08-05 14:58 ` [PATCH] ui: 'package->recutils' serializes the source field David Craven
2016-08-06 12:35 ` Alex Kost
2016-08-06 12:46 ` David Craven
2016-08-06 15:00 ` Mathieu Lirzin
2016-08-07 10:26 ` David Craven
2016-08-07 11:15 ` Mathieu Lirzin
2016-08-07 11:19 ` David Craven
2016-08-07 12:12 ` David Craven
2016-08-07 13:27 ` Mathieu Lirzin
2016-08-07 21:33 ` David Craven
2016-08-08 0:15 ` Mathieu Lirzin
2016-08-08 11:20 ` David Craven
2016-08-08 17:53 ` Mathieu Lirzin
2016-08-08 18:12 ` David Craven
2016-08-08 19:07 ` Alex Kost
2016-08-08 21:09 ` Mathieu Lirzin
2016-08-08 22:58 ` David Craven
2016-08-08 23:56 ` Mathieu Lirzin
2016-08-09 0:18 ` David Craven
2016-08-10 10:12 ` David Craven
2016-08-10 11:30 ` Mathieu Lirzin
2016-08-10 11:38 ` David Craven
2016-08-10 11:46 ` David Craven
2016-08-10 12:06 ` Mathieu Lirzin
2016-08-10 12:15 ` Ben Woodcroft
2016-08-10 12:27 ` David Craven
2016-08-10 12:53 ` Ben Woodcroft
2016-08-10 13:23 ` David Craven
2016-08-10 13:42 ` Ricardo Wurmus
2016-08-10 14:13 ` David Craven
2016-08-11 14:38 ` Alex Kost
2016-08-11 16:19 ` David Craven
2016-08-11 18:15 ` Ricardo Wurmus
2016-08-12 8:22 ` Alex Kost
2016-08-11 16:42 ` Ricardo Wurmus
2016-08-12 8:33 ` Alex Kost [this message]
2016-08-12 8:41 ` Ricardo Wurmus
2016-08-12 10:05 ` David Craven
2016-08-13 7:46 ` Alex Kost
2016-08-13 13:00 ` David Craven
2016-08-13 13:18 ` Leo Famulari
2016-08-14 16:00 ` Alex Kost
2016-08-10 14:25 ` Thompson, David
2016-08-10 17:56 ` Leo Famulari
2016-08-11 10:15 ` Mark H Weaver
2016-08-11 10:21 ` Mark H Weaver
2016-08-11 11:06 ` David Craven
2016-08-11 11:41 ` Mark H Weaver
2016-08-11 11:46 ` David Craven
2016-08-10 11:46 ` How to get the package metadata as structured data? Ricardo Wurmus
2016-08-10 12:14 ` Catonano
2016-08-10 12:52 ` Ricardo Wurmus
2016-08-10 23:40 ` Catonano
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=87lh02gzeo.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=david@craven.ch \
--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 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.