unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Leo Prikler <leo.prikler@student.tugraz.at>,
	john.kehayias@protonmail.com, 50103@debbugs.gnu.org
Subject: bug#50103: Pulseaudio doesn't export XDG_CONFIG_DIRS
Date: Wed, 18 Aug 2021 11:28:32 +0200	[thread overview]
Message-ID: <04f0f93cb3dd7fa70d940f200b00432eaf9004e9.camel@telenet.be> (raw)
In-Reply-To: <8260714867d007d924c151a18ff9c63950ab2fcd.camel@student.tugraz.at>

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

Leo Prikler schreef op wo 18-08-2021 om 10:03 [+0200]:
> Hi John,
> 
> a lot of packages would do much better if they exported
> XDG_CONFIG_DIRS.  However, there is currently no way of doing so other
> than copypasting the same snippet over and over and over and over.  A
> workaround -- if you need this in an environment -- is to also include
> a package, that already has a search path on XDG_CONFIG_DIRS, like glib
> (I think glib:bin works too).
> 
> I recently tried exporting XDG_CONFIG_DIRS as a variable from one
> module, so that it can be referenced in others, but that led to a weird
> recursive errors.  It would be nice to find a good way of doing that,
> though.

What do you think of defining the <search-path-specification>
$XDG_CONFIG_DIR in (guix search-paths) itself, next to $PATH?  That seems
unlikely to lead to recursive errors.

Alternatively, I would guess that making 'search-paths' and
'native-search-paths' a ‘thunked’ field would resolve the errors,
at cost of making <package> objects use a bit more memory.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-08-18  9:29 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 [this message]
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

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=04f0f93cb3dd7fa70d940f200b00432eaf9004e9.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --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).