From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>, 54454@debbugs.gnu.org
Subject: [bug#54454] [PATCH] ui: Describe package outputs.
Date: Fri, 18 Mar 2022 21:25:25 +0100 [thread overview]
Message-ID: <1730db1e84a3b1529c148840e995794a2f57f216.camel@gmail.com> (raw)
In-Reply-To: <dfeccaf27d201c708588b8599067eb4f75ee6c12.camel@telenet.be>
Am Freitag, dem 18.03.2022 um 21:16 +0100 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op vr 18-03-2022 om 20:16 [+0100]:
> > + (G_ "state secrets.")))))
>
> Wouldn't this require #:substitutable? #false?
> It's punny but rather inaccurate ...
You can substitute state secrets, but they will be marked to see who
leaked them. It's not like all of our outputs are 100% reproducible,
are they? :P
> WDYT of adding a package property to allow packages to document
> unusual outputs?
That is literally the first thing I'm doing. It is unimaginatively
called 'output-descriptions and checked before either of the fallbacks.
Cheers
next prev parent reply other threads:[~2022-03-18 20:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 19:16 [bug#54454] [PATCH] ui: Describe package outputs Liliana Marie Prikler
2022-03-18 20:12 ` Maxime Devos
2022-03-18 20:23 ` Liliana Marie Prikler
2022-03-18 20:16 ` Maxime Devos
2022-03-18 20:25 ` Liliana Marie Prikler [this message]
2022-03-18 20:50 ` Maxime Devos
2022-03-18 20:54 ` Maxime Devos
2022-03-18 22:24 ` Liliana Marie Prikler
2022-03-18 22:57 ` Maxime Devos
2022-03-18 23:27 ` Liliana Marie Prikler
2022-03-19 8:56 ` Maxime Devos
2022-03-19 10:48 ` Ludovic Courtès
2022-03-19 16:24 ` Leo Famulari
2022-06-26 12:37 ` [bug#54454] [PATCH v2] " Liliana Marie Prikler
2022-08-16 19:37 ` bug#54454: " Liliana Marie Prikler
2022-09-02 17:07 ` [bug#54454] " Ludovic Courtès
2022-09-02 17:14 ` Liliana Marie Prikler
2022-09-03 9:53 ` zimoun
2022-09-05 7:25 ` 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
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=1730db1e84a3b1529c148840e995794a2f57f216.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=54454@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).