From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Data Services: use cases
Date: Mon, 16 Nov 2020 19:17:39 +0000 [thread overview]
Message-ID: <87sg99m7qk.fsf@cbaines.net> (raw)
In-Reply-To: <868scbvalo.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Chris,
>
> Since blog post about Data Services seems floating around, I describe
> what I find useful as an end-user of the service. And if you have not
> showed me IRL at FOSDEM (and you showed me several times ;-)), then I
> would not be using the service so often.
...
> Well, I could describe other use cases, but I think this one is really
> useful for the end-user:
>
> - list all the versions available (since Dec. 2019 I guess)
> - know which build and which not
> - easily find the commit for “guix time-machine”
Thanks for putting this together Simon.
Something I've been thinking about in relation to this is making this
information more available. The Guix Data Service tries to structure the
data in a sensible manor, which doesn't always best fit how people most
often want to use it.
Maybe there could be a packages.guix.gnu.org service which pulls
together information about packages to meet the common needs that users
of Guix have. Things like:
- Searching for packages by name
- Looking at version availability
- Looking at build success/substitute availability
Thanks again,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2020-11-16 19:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 13:26 Data Services: use cases zimoun
2020-10-13 8:44 ` Pierre Neidhardt
2020-10-21 9:27 ` Ludovic Courtès
2020-10-21 9:39 ` Pierre Neidhardt
2020-10-21 10:19 ` zimoun
2020-11-16 19:28 ` Christopher Baines
2020-11-16 20:24 ` zimoun
2020-11-16 20:54 ` Christopher Baines
2020-11-16 21:12 ` zimoun
2020-11-16 21:50 ` Christopher Baines
2020-11-16 22:38 ` zimoun
2020-11-17 21:43 ` zimoun
2020-11-17 21:57 ` Fix incorrect date and commit in Data Service zimoun
2020-11-17 22:44 ` zimoun
2020-11-16 19:26 ` Data Services: use cases Christopher Baines
2020-11-16 19:20 ` Christopher Baines
2020-11-17 7:48 ` Pierre Neidhardt
2020-11-17 8:04 ` Christopher Baines
2020-11-17 8:49 ` Pierre Neidhardt
2020-11-17 19:34 ` Christopher Baines
2020-11-17 19:42 ` Pierre Neidhardt
2020-11-16 19:17 ` Christopher Baines [this message]
2020-11-16 20:34 ` zimoun
2020-11-16 21:08 ` Christopher Baines
2020-11-17 13:19 ` Linking to the data service Ludovic Courtès
2020-11-17 16:26 ` zimoun
2020-11-17 16:18 ` Data Services: use cases zimoun
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=87sg99m7qk.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@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).