all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ellis Kenyő via Guix-patches via" <guix-patches@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 46215@debbugs.gnu.org
Subject: [bug#46215] [PATCH] Add yadm
Date: Sat, 06 Feb 2021 11:26:59 +0000	[thread overview]
Message-ID: <330eb3b4-1e90-4c0e-bb83-a8bd2cd81365@elken.dev> (raw)
In-Reply-To: <78f1ced9e2125994a806383fb1d985d256874a81.camel@student.tugraz.at>

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

I'm not at all fixated on a minimal package and I resent the idea of putting minimal effort in.

I was purely asking a simple question, there's no need to resort to rudeness.

On 6 Feb 2021, 11:22, at 11:22, Leo Prikler <leo.prikler@student.tugraz.at> wrote:
>Am Samstag, den 06.02.2021, 10:58 +0000 schrieb Ellis Kenyő:
>> > As long as it can reasonably be expected, that users will want it,
>> > yes.
>> > If the soft dependency is indeed completely optional, the software
>> > works perfectly fine without it and few people will be negatively
>> > impacted by a minor feature missing, then it's fine to leave it
>> > as-is
>>
>> This is the only point I'm making. Things like templates and
>> encryption aren't used by everyone so could definitely be optional,
>> so I was asking if there was a simple way to handle optional inputs.
>> As it doesn't seem like there is I'll just add everything required.
>I'd like to say "use your best judgement", but you seem to be a little
>too fixated on having a minimal package description (and putting
>minimal effort into it).  For instance, when the package advertises
>encryption, while it is technically optional, shipping it without gpg
>would be a grave oversight!  (On the other hand, you need not
>necessarily have openssl, since encryption requires any of gpg or
>openssl, not both.)  Same for templates, at least awk is required and
>either j2cli or envtpl would be nice to have.
>
>Regards,
>Leo

[-- Attachment #2: Type: text/html, Size: 2113 bytes --]

  reply	other threads:[~2021-02-06 11:28 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=330eb3b4-1e90-4c0e-bb83-a8bd2cd81365@elken.dev \
    --to=guix-patches@gnu.org \
    --cc=46215@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=me@elken.dev \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.