From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 56127@debbugs.gnu.org
Subject: [bug#56127] [PATCH] gnu: polybar: Update to 3.6.3.
Date: Wed, 22 Jun 2022 14:35:00 +0000 [thread overview]
Message-ID: <FPLRbSend_Y1e2dGrHvf8hJaACaz52k3wktjRZJ3QMzXIO6vBtxcA04Ig8heWmKLEUbjSBrVFQVier08v9vmd5Kc3g6MLBOZSyF2OH7bN6U=@protonmail.com> (raw)
In-Reply-To: <878rpou84l.fsf@jpoiret.xyz>
Hi Josselin,
------- Original Message -------
On Wednesday, June 22nd, 2022 at 9:42 AM, Josselin Poiret <dev@jpoiret.xyz> wrote:
>
> Looks good to me as-is, builds and runs fine, although I'd prefer to
> keep the file at /etc/, and patch src/utils/file.cpp to look for
> $output/etc/polybar/config.ini. That way, polybar would work without a
> config file even when not installed. Also, if you have the time, could
> you move the native-inputs to the new style as an additional commit?
>
> WDYT?
Not sure I understand what you mean by not needing to have polybar installed. Do you mean not having to worry about XDG_CONFIG_DIRS being set up? Running directly from /gnu/store? I can make that change (it was the alternative I thought of too) if that would help useability for a new user without a config.
And yes, can update with a second commit to clean native-inputs as well.
Thanks for taking a look!
John
next prev parent reply other threads:[~2022-06-22 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 18:21 [bug#56127] [PATCH] gnu: polybar: Update to 3.6.3 John Kehayias via Guix-patches via
2022-06-22 13:42 ` Josselin Poiret via Guix-patches via
2022-06-22 14:35 ` John Kehayias via Guix-patches via [this message]
2022-06-23 10:16 ` Josselin Poiret via Guix-patches via
2022-06-23 14:40 ` [bug#56127] [PATCH 1/2 v2] " John Kehayias via Guix-patches via
2022-06-23 20:29 ` bug#56127: [PATCH] " Ludovic Courtès
2022-06-23 14:41 ` [bug#56127] [PATCH 2/2] gnu: polybar: Simplify inputs John Kehayias 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='FPLRbSend_Y1e2dGrHvf8hJaACaz52k3wktjRZJ3QMzXIO6vBtxcA04Ig8heWmKLEUbjSBrVFQVier08v9vmd5Kc3g6MLBOZSyF2OH7bN6U=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=56127@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=john.kehayias@protonmail.com \
/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.