From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 32121@debbugs.gnu.org
Subject: [bug#32121] [PATCH 4/5] database: Call a specification 'jobset' instead of 'project'.
Date: Fri, 13 Jul 2018 13:56:28 +0200 [thread overview]
Message-ID: <87y3efic2b.fsf@gnu.org> (raw)
In-Reply-To: <87wotz1nso.fsf@lassieur.org> ("Clément Lassieur"'s message of "Fri, 13 Jul 2018 11:35:03 +0200")
Clément Lassieur <clement@lassieur.org> skribis:
> This will somehow break a minor part of Tatiana's work because the main
> page will look like
>
> Projects/Specifications
>
> | Name | Branch |
> |--------------+--------------|
> | guix-modular | master |
> | guix-modular | core-updates |
>
>
> instead of
>
> Projects/Specifications
>
> | Name |
> |---------------------------|
> | guix-modular-master |
> | guix-modular-core-updates |
So we’d be moving the project/branch structure to naming conventions.
In a way, that’s not great, because as users we like to think in terms
of branches to answer questions like “how many packages failed in branch
X of the Savannah repo?”.
However, this can probably be addressed at the UI level: the web UI and
guix-hydra.el could list (shortened) repo URLs and branch names instead
of this ‘name’ field. Eventually, we could remove this ‘name’ field
altogether and instead have an automatically-assigned numerical ID.
WDYT?
(This does not affect this patch series, I’m thinking about what we can
do eventually.)
> However, we could still be able to bind a specification to a branch, but
> that would require adding a 'guix-input' specification field, so that
> the specification knows which input is the one whose branch should be
> displayed. I doubt it's worth it though. Or we could replace the
> 'load-path-inputs' field with a 'guix-input' field. That was kind of
> the point of the 3rd part of my initial message[1]. Or, we could
> automate things: find out from which input the Guix modules come. That
> would be a bit tricky.
Oh right, since we now have multiple inputs, what I wrote above is not
quite true; there can be several repo URLs/branches that would need to
be shown on the UI. Hmm, maybe we need to keep the ‘name’, but only as
a hint and not as a key.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-07-13 11:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 22:58 [bug#32121] Cuirass: add support for multiple inputs Clément Lassieur
2018-07-10 23:02 ` [bug#32121] [PATCH 1/5] base: Compile CHECKOUT in the fiber Clément Lassieur
2018-07-10 23:02 ` [bug#32121] [PATCH 2/5] utils: Reset the Fiber dynamic environment in %NON-BLOCKING Clément Lassieur
2018-07-13 8:35 ` Ludovic Courtès
2018-07-14 12:13 ` Clément Lassieur
2018-07-14 13:45 ` Ludovic Courtès
2018-07-10 23:02 ` [bug#32121] [PATCH 3/5] database: Add support for database upgrades Clément Lassieur
2018-07-13 8:47 ` Ludovic Courtès
2018-07-14 15:00 ` Clément Lassieur
2018-07-14 15:32 ` Clément Lassieur
2018-07-16 13:17 ` Ludovic Courtès
2018-07-10 23:02 ` [bug#32121] [PATCH 4/5] database: Call a specification 'jobset' instead of 'project' Clément Lassieur
2018-07-13 8:51 ` Ludovic Courtès
2018-07-13 9:35 ` Clément Lassieur
2018-07-13 9:43 ` Clément Lassieur
2018-07-13 11:56 ` Ludovic Courtès [this message]
2018-07-14 19:57 ` Clément Lassieur
2018-07-10 23:02 ` [bug#32121] [PATCH 5/5] Add support for multiple inputs Clément Lassieur
2018-07-13 9:28 ` Ludovic Courtès
2018-07-15 8:25 ` Clément Lassieur
2018-07-16 20:13 ` bug#32121: " Clément Lassieur
2018-07-13 8:32 ` [bug#32121] [PATCH 1/5] base: Compile CHECKOUT in the fiber Ludovic Courtès
2018-07-13 8:55 ` Clément Lassieur
2018-07-13 11:50 ` Ludovic Courtès
2018-07-13 11:57 ` Clément Lassieur
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=87y3efic2b.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=32121@debbugs.gnu.org \
--cc=clement@lassieur.org \
/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).