unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Divya Ranjan via "Development of GNU Guix and the GNU System
	distribution." <guix-devel@gnu.org>
Cc: Divya Ranjan <divya@subvertising.org>
Subject: Re: Using Pipewire for PulseAudio and JACK in Guix
Date: Sun, 03 Nov 2024 12:50:42 +0100	[thread overview]
Message-ID: <87ed3silil.fsf@elephly.net> (raw)
In-Reply-To: <87fro8rgbp.fsf@subvertising.org> (Divya Ranjan via's message of "Sun, 03 Nov 2024 06:18:02 +0000")

Divya Ranjan via "Development of GNU Guix and the GNU System 
distribution." <guix-devel@gnu.org> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Divya <divya@subvertising.org> writes:
>>
>>> Thanks for pointing it out, indeed its trying to write into
>>> /etc/xdg.
>>> How does one handle such a case when packaging in Guix?
>>
>> We'd patch the build system files to make it write to 
>> $output/etc/xdg
>> instead.
>
> But wouldn’t that break with updates? Or, does one need to 
> update the
> build system files everytime with a release?

No, you'd use a G-expression and refer to #$output in the build 
phase.
#$output will always have the value of the output directory.

> Do you think one should
> send a patch for this to the source tree, to make it compatible 
> with
> both Guix and Non-Guix GNU/Linux distributions?

No need.  Just patch it in a custom build phase.

-- 
Ricardo


  reply	other threads:[~2024-11-03 11:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 13:27 Using Pipewire for PulseAudio and JACK in Guix Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-10-28 13:46 ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-11-01  7:31   ` Ricardo Wurmus
2024-11-02 13:36     ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-11-02 16:08       ` Kaelyn via Development of GNU Guix and the GNU System distribution.
2024-11-02 17:18         ` Divya
2024-11-02 23:00           ` Ricardo Wurmus
2024-11-03  6:18             ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-11-03 11:50               ` Ricardo Wurmus [this message]
2024-11-13 13:10                 ` divya
2024-12-15 11:26                   ` Maxim Cournoyer
2024-11-07  9:41             ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-10-31 18:19 ` Divya
  -- strict thread matches above, loose matches on Subject: below --
2024-11-01 13:11 Noé Lopez via Development of GNU Guix and the GNU System distribution.
2024-11-03  6:21 ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.

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=87ed3silil.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=divya@subvertising.org \
    --cc=guix-devel@gnu.org \
    /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).