From: Sergey Trofimov <sarg@sarg.org.ru>
To: lgcoelho@disroot.org
Cc: ludovic.courtes@inria.fr, 68010@debbugs.gnu.org
Subject: [bug#68010] [PATCH] home: services: Add home-zathura-service-type.
Date: Tue, 26 Dec 2023 10:33:16 +0100 [thread overview]
Message-ID: <874jg5gvfn.fsf@sarg.org.ru> (raw)
In-Reply-To: <a4e1ffea3e66951afff930078db97976@disroot.org>
lgcoelho@disroot.org writes:
> This service enables a declarative configuration of zathura, the
> customizable document viewer.
I have mixed feelings about pulling 3rd-party software
configurations in guix:
- adding it to guix increases maintenance burden: new versions
could add or remove config options
- it bloats guix: imagine if we add configs for every
user-configurable app
- such configs are not easily transferrable: if I were to use the
same app in non-guix env, I'd have to maintain 2 configs
Another recent example is `oci-container-configuration` which
defines a subset of docker-cli startup arguments. The problem is
that `docker run` command has 96 options and the configuration
only uses a handful, lacking a way to provide the remaining ones.
I think guix should not embed config generators for user software.
The only need I see for such generators is when there are options
which should be the same among multiple applications (e.g. color
schemes or shared directories). For such usecase guix should
provide better text manipulation tools which home owners could use
to parameterise configs.
next prev parent reply other threads:[~2023-12-26 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 18:26 [bug#68010] [PATCH] home: services: Add home-zathura-service-type lgcoelho--- via Guix-patches via
2023-12-26 9:33 ` Sergey Trofimov [this message]
2023-12-26 12:11 ` Oleg Pykhalov
2024-01-08 8:46 ` Ludovic Courtès
2024-01-23 13:09 ` Oleg Pykhalov
2024-01-23 13:13 ` Oleg Pykhalov
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=874jg5gvfn.fsf@sarg.org.ru \
--to=sarg@sarg.org.ru \
--cc=68010@debbugs.gnu.org \
--cc=lgcoelho@disroot.org \
--cc=ludovic.courtes@inria.fr \
/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).