all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: units_cur
Date: Sat, 31 Mar 2018 19:10:43 +0200	[thread overview]
Message-ID: <87bmf4jhm4.fsf@gnu.org> (raw)
In-Reply-To: <87370ggpwc.fsf@gmail.com> (Pierre Neidhardt's message of "Sat, 31 Mar 2018 22:10:03 +0530")

Pierre Neidhardt <ambrevar@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hmm, dunno.  Perhaps we could modify ‘units’ to look for
>> /var/run/units/currency.units first, and fall back to
>> /gnu/store/…-units/share/units/currency.units.
>>
>> We would also arrange for ‘units_cur’ to update the file in /var/run by
>> default.
>>
>> WDYT?
>
> That sounds reasonable to me.  What's the purpose of /var/run on GuixSD?
> How is it used?

On GNU/Linux /var/run is the standard location to store “state” files.
See ‘runstatedir’ in
<https://www.gnu.org/prep/standards/html_node/Directory-Variables.html>.

Ludo’.

  reply	other threads:[~2018-03-31 17:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 10:11 units_cur Pierre Neidhardt
2018-03-27 21:01 ` units_cur Ludovic Courtès
2018-03-30 11:15   ` units_cur Pierre Neidhardt
2018-03-30 16:33     ` units_cur Ludovic Courtès
2018-03-31  4:37       ` units_cur Pierre Neidhardt
2018-03-31 16:18         ` units_cur Ludovic Courtès
2018-03-31 16:40           ` units_cur Pierre Neidhardt
2018-03-31 17:10             ` Ludovic Courtès [this message]
2018-04-01  6:16               ` units_cur Pierre Neidhardt
2018-04-01 13:06                 ` units_cur Pierre Neidhardt
2018-04-01 13:37                   ` units_cur Mathieu Lirzin
2018-03-31  4:51       ` units_cur Pierre Neidhardt
2018-03-31  7:01         ` units_cur Pierre Neidhardt
2018-03-31 16:16           ` units_cur Ludovic Courtès

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=87bmf4jhm4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=ambrevar@gmail.com \
    --cc=help-guix@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 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.