Hi !

I'm trying to let users reconfigure their home configuration on a shared
guix system, but we can't all have a 700MB .cache/guix dir. I've solved
part of the problem by forbidding guix pull and deploying an up-to-date
system wide guix regularly.

However, when running guix home reconfigure config.scm, with config.scm
containing the most empty home configuration in the history of empty
home configurations:

#+begin_src scheme
(use-modules (beaver home)
             (gnu home))

(-> (home-environment
      (packages '())
      (essential-services '())
      (services '())
      (location #f)))
#+end_src

guix dutifully pulls the whole guix repo into the cache :/

I know there is a system service I can use to deploy the home
configuration too, but this makes us lose the flexibility of having a
user-configurable home.

I think I'll maintain a systemwide cache as a workaround, but any
guidance as to why guix home needs a full copy of the whole history of
guix would help me understand how to get rid of that.


Thanks in advance.

Edouard.

Reply via email to