all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Brian Cully <bjc@spork.org>
Cc: guix-devel@gnu.org, Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: Re: GNU Shepherd 0.9.0 released
Date: Sun, 10 Apr 2022 22:36:14 +0200	[thread overview]
Message-ID: <87sfqk4qwx.fsf@gnu.org> (raw)
In-Reply-To: <87pmltasms.fsf@ditto.jhoto.spork.org> (Brian Cully's message of "Thu, 07 Apr 2022 10:11:47 -0400")

Hi,

(Stripping Cc: list.)

Brian Cully <bjc@spork.org> skribis:

> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>
>> Am Mittwoch, dem 06.04.2022 um 23:25 +0200 schrieb Ludovic Courtès:
>>>   ** Log file of unprivileged ‘shepherd’ is now under $XDG_DATA_DIR
>> Should that not be $XDG_STATE_DIR?
>
> 	I believe it should be $XDG_STATE_HOME, in fact. See:
> 	https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
>
> ---[snip]---
>  $XDG_STATE_HOME defines the base directory relative to which
>  user-specific state files should be stored. If $XDG_STATE_HOME is
>  either not set or empty, a default equal to $HOME/.local/state should
>  be used.
>  ---[snip]---

I was referring to this commit:

  https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=c6382a6898f2851d78b675f209787c5ff9ad4320

But actually a later commit uses XDG_STATE_HOME:

  https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=ec2a0b07a6dedcbec3cf6bb7328b144a117873e8

So I guess I just got confused and made a mistake in ‘NEWS’?

Ludo’.


  reply	other threads:[~2022-04-10 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 21:25 GNU Shepherd 0.9.0 released Ludovic Courtès
2022-04-06 23:18 ` Zhu Zihao
2022-04-07  4:12 ` Liliana Marie Prikler
2022-04-07 14:11   ` Brian Cully
2022-04-10 20:36     ` Ludovic Courtès [this message]
2022-04-09 22:14 ` bug#54828: ssh disconnects when reconfiguring system Vagrant Cascadian
2022-04-10 17:37   ` Vagrant Cascadian

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=87sfqk4qwx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bjc@spork.org \
    --cc=guix-devel@gnu.org \
    --cc=liliana.prikler@gmail.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.