[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to deal with system-wide state databases
From: |
Ludovic Courtès |
Subject: |
Re: How to deal with system-wide state databases |
Date: |
Mon, 13 Jun 2016 17:11:57 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Roel Janssen <address@hidden> skribis:
> Ludovic Courtès writes:
>
>> Hello!
>>
>> Roel Janssen <address@hidden> skribis:
>>
>>> How should we deal with mechanisms like this? Should I change the
>>> scrollkeeper
>>> database directory per program, so in this case it becomes:
>>> /gnu/store/xgbvyqs...-gparted-0.26.0/var/lib/scrollkeeper
>>>
>>> Or can we deal with this in a more cross-package way?
>>
>> Maybe we could add a profile hook to ‘%default-profile-hooks’ in (guix
>> profiles)?
>
> I think people only need Scrollkeeper when they wish to have the
> documentation available in Yelp (GNOME's help browser). So it only
> affects a few people I believe.
I think documentation is quite useful, in general. :-)
> Would it then still make sense? Maybe this hook should only be active
> when Yelp is installed in the profile on which the transaction
> operates. Is that possible?
Definitely. For instance, ‘ghc-package-cache-file’ does exactly this
kind of trick. (It’s not completely satisfying, since we’re simply
matching file names, but it does the job.)
> With this construct, I'd have to patch out the 'scrollkeeper-update'
> command from the GParted build system.
Yes.
Thanks,
Ludo’.