unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: rg@raghavgururajan.name, 66339@debbugs.gnu.org,
	Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: bug#66339: Gnome-team dbus socket in /var/run/dbus, not /run/dbus
Date: Sat, 07 Oct 2023 10:39:37 -0400	[thread overview]
Message-ID: <87y1geijiu.fsf_-_@gmail.com> (raw)
In-Reply-To: <0f234811bdabf42660367dfae5ecdf88439b48e3.1696688485.git.vivien@planete-kraus.eu> (Vivien Kraus's message of "Fri, 6 Oct 2023 23:12:50 +0200")

Hi,

Vivien Kraus <vivien@planete-kraus.eu> writes:

> Glib has made /run the default runstatedir:
>
> https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3101
>
> However, in Guix, the default runstatedir is /var/run.
>
> * gnu/packages/glib.scm (glib): Set runtime_dir to /var/run.
> ---
>
> I changed my mind again!  Following the IRC discussion, Guix has a separate
> /var/run and /run (and puts /run/current-system/ in /run).  So, /var/run/dbus
> is actually the correct place to put the system session socket.

I don't follow; why does it matter that Guix puts its current-system
directory under /run?  /run is to be shared by many applications, like
/tmp, no?

I still see /var/run as the legacy directory of /run, so I'd prefer we
standardize to use the modern variant to reduce this kind of friction
with the applications which will only grow in the future.

-- 
Thanks,
Maxim




  reply	other threads:[~2023-10-07 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3121a39dc569ff872afe74a8871ef71456ea5451.camel@univ-reims.fr>
2023-10-04 10:47 ` bug#66339: [WIP PATCH gnome-team] gnu: dbus-service: make the session available under /run/dbus Vivien Kraus via Bug reports for GNU Guix
2023-10-04 18:30   ` Liliana Marie Prikler
2023-10-04 10:47     ` bug#66339: [PATCH gnome-team v2] " Vivien Kraus via Bug reports for GNU Guix
2023-10-05  4:41       ` Liliana Marie Prikler
2023-10-04 10:47         ` bug#66339: [PATCH gnome-team v3] " Vivien Kraus via Bug reports for GNU Guix
2023-10-06 18:50           ` Liliana Marie Prikler
2023-10-04 10:47             ` bug#66339: [PATCH gnome-team v4] " Vivien Kraus via Bug reports for GNU Guix
2023-10-06 21:41               ` Liliana Marie Prikler
2023-10-04 10:47                 ` bug#66339: [PATCH gnome-team v6] " Vivien Kraus via Bug reports for GNU Guix
2023-10-08 14:53                   ` Liliana Marie Prikler
2023-10-09 20:36                     ` Liliana Marie Prikler
2023-10-06 21:12                 ` bug#66339: [PATCH gnome-team v5] gnu: glib: Set runstatedir Vivien Kraus via Bug reports for GNU Guix
2023-10-07 14:39                   ` Maxim Cournoyer [this message]
2023-10-08 15:40                     ` bug#66339: Gnome-team dbus socket in /var/run/dbus, not /run/dbus Bruno Victal

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=87y1geijiu.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=66339@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=rg@raghavgururajan.name \
    --cc=vivien@planete-kraus.eu \
    /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).