GNU bug report logs - #46215
[PATCH] Add yadm

Previous Next

Full log

Message #50 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ellis Kenyő <me <at> elken.dev>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: Leo Prikler <leo.prikler <at> student.tugraz.at>, 46215 <at> debbugs.gnu.org,
 guix-patches <at> gnu.org
Subject: Re: [bug#46215] [PATCH] Add yadm
Date: Sat, 06 Feb 2021 11:43:28 +0000

[Message part 1 (text/plain, inline)]

Hi Tobias,

Yes I am aware that it's more complicated than the initial question, I'm fine with adding all the dependencies as inputs.

I was simply asking the correct way to handle optional inputs.

> Does that not work?

Yes it would absolutely work, I have tested as such in depth on multiple guix systems.

> For things like templates {native-,}search-paths can be a
solution, depending on how yadm (or its templating library)
searches for these.

Yes I still have further testing with regards to templates as I don't personally use them.

Thanks you for your input Tobias

On 6 Feb 2021, 11:37, at 11:37, Tobias Geerinckx-Rice <me <at> tobias.gr> wrote:
>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

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.