From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: "Ellis Kenyő" <me@elken.dev>
Cc: leo.prikler@student.tugraz.at, 46215@debbugs.gnu.org
Subject: [bug#46215] [PATCH] Add yadm
Date: Sat, 06 Feb 2021 12:30:22 +0100 [thread overview]
Message-ID: <871rdtxwkx.fsf@nckx> (raw)
In-Reply-To: <9b32a7b7-9664-4108-a66c-f3de42d10c68@elken.dev>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Ellis,
Ellis Kenyő via Guix-patches via 写道:
> I was asking if there was a simple way to handle optional
> inputs.
While this is an oxymoron for the reasons pointed out by Leo,
there is _nothing_ wrong with simply leaving some variables at
their default e.g.
GPG_PROGRAM="gpg"
and letting yadm look them up at run time in its $PATH.
Does that not work?
For things like templates {native-,}search-paths can be a
solution, depending on how yadm (or its templating library)
searches for these.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-02-06 11:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 16:47 [bug#46215] [PATCH] Add yadm guix-patches--- via
2021-01-31 17:38 ` Leo Prikler
2021-01-31 20:16 ` guix-patches--- via
2021-01-31 20:36 ` Leo Prikler
2021-02-01 3:44 ` guix-patches--- via
2021-02-01 8:13 ` Leo Prikler
2021-02-01 10:06 ` guix-patches--- via
2021-02-01 11:44 ` Leo Prikler
2021-02-06 10:05 ` Ellis Kenyő via Guix-patches via
2021-02-06 10:48 ` Leo Prikler
2021-02-06 10:58 ` Ellis Kenyő via Guix-patches via
2021-02-06 11:22 ` Leo Prikler
2021-02-06 11:26 ` Ellis Kenyő via Guix-patches via
2021-02-06 11:46 ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-06 12:41 ` Leo Prikler
2021-02-06 11:30 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2021-02-06 11:43 ` Ellis Kenyő via Guix-patches via
2021-02-06 11:58 ` Leo Prikler
2021-02-06 12:03 ` Tobias Geerinckx-Rice via Guix-patches via
2022-09-09 0:01 ` [bug#46215] [PATCH] gnu: " kiasoc5 via Guix-patches via
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=871rdtxwkx.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=46215@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=me@elken.dev \
--cc=me@tobias.gr \
/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).