From: zimoun <zimon.toutoune@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>,
John Kehayias <john.kehayias@protonmail.com>
Cc: 50103@debbugs.gnu.org
Subject: bug#50103: Pulseaudio doesn't export XDG_CONFIG_DIRS
Date: Fri, 20 Aug 2021 11:44:06 +0200 [thread overview]
Message-ID: <865yw0pi1l.fsf@gmail.com> (raw)
In-Reply-To: <870c9fb6c492092ef3b5b41b007c160be423fc69.camel@student.tugraz.at>
Hi,
On Wed, 18 Aug 2021 at 18:35, Leo Prikler <leo.prikler@student.tugraz.at> wrote:
> Am Mittwoch, den 18.08.2021, 16:06 +0000 schrieb John Kehayias:
>> .config/guix is hardcoded in a few places already isn't it? (or is
>> that just for root? took just a quick look) Personally, I prefer
>> everything in .config to keep the home folder cleaner, but we all
>> know there's a strong mix of things like $HOME/.something and
>> $HOME/.config/something.
> $(HOME)/.config is particularly hard-coded in the current /etc/profile,
> which is why I dub it "fake XDG conformance". I personally disagree
> with the use for $(HOME)/.config for software packages.
Well, let open a new thread and resume the previous discussion should
nice. From what I remember, the consensus had been (almost) reached and
none of us took the time to propose a draft patch. :-)
We could imagine a hierarchy where the profile are looked for––say
~/.cache/guix/profiles/ then ~/.config/guix/profiles then etc.––or an
environment variable to let the user have the control. Whatever, we all
have an idea but nothing concrete to discussion the details. ;-)
From my understanding, set a central place where the profiles live would
be very helpful. Having only one big profile slows down a lot of
operation when several ones ease the maintenance, IMHO.
Cheers,
simon
PS: Personally, I have profiles with my tools (Emacs, notmuch,
etc. )under ~/.config/guix/profiles and these profiles are generated
with manifests under ~/.config/guix/manifests/ (folder under Git). Then
inside each project, I have a manifest file specific for the project,
then sometime the profile lives here, sometime I only use “guix
environment”, etc.
prev parent reply other threads:[~2021-08-20 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 5:07 bug#50103: Pulseaudio doesn't export XDG_CONFIG_DIRS John Kehayias via Bug reports for GNU Guix
2021-08-18 8:03 ` Leo Prikler
2021-08-18 9:28 ` Maxime Devos
2021-08-18 9:45 ` Leo Prikler
2021-08-18 14:27 ` John Kehayias via Bug reports for GNU Guix
2021-08-18 15:19 ` Leo Prikler
2021-08-18 16:06 ` John Kehayias via Bug reports for GNU Guix
2021-08-18 16:35 ` Leo Prikler
2021-08-18 17:53 ` John Kehayias via Bug reports for GNU Guix
2021-08-20 9:44 ` zimoun [this message]
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=865yw0pi1l.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=50103@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=leo.prikler@student.tugraz.at \
/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).