Re: How to deal with system-wide state databases

2016-06-14 Thread Ludovic Courtès
Roel Janssen skribis: > Ludovic Courtès writes: [...] >>> With this construct, I'd have to patch out the 'scrollkeeper-update' >>> command from the GParted build system. >> >> Yes. > > Great. So the next step with GParted is to create a > 'scrollkeeper-database' hook. I'm not sure how to do t

Re: How to deal with system-wide state databases

2016-06-13 Thread Roel Janssen
Ludovic Courtès writes: > Roel Janssen skribis: > >> Ludovic Courtès writes: >> >>> Hello! >>> >>> Roel Janssen 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/stor

Re: How to deal with system-wide state databases

2016-06-13 Thread Ludovic Courtès
Roel Janssen skribis: > Ludovic Courtès writes: > >> Hello! >> >> Roel Janssen 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/scr

Re: How to deal with system-wide state databases

2016-06-13 Thread Roel Janssen
Ludovic Courtès writes: > Hello! > > Roel Janssen 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 wit

Re: How to deal with system-wide state databases

2016-06-10 Thread Ludovic Courtès
Hello! Roel Janssen 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? M

How to deal with system-wide state databases

2016-06-10 Thread Roel Janssen
Dear Guix, I've been trying to get the help feature in gparted to work, but it uses an external program for it called "scrollkeeper". No problem so far, because I have a working package for it. However, Scrollkeeper maintains a database in which all documentation that is compatible with scrollke