From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Defining user services in Guix. Date: Thu, 27 Apr 2017 15:36:51 +0200 Message-ID: <8737cu7z0s.fsf@gnu.org> References: <87o9vowfn0.fsf@gmail.com> <20170422203131.610f2a30@scratchpost.org> <878tmsghzk.fsf@gnu.org> <87inlvdr76.fsf@gmail.com> <87r30hbbi7.fsf@gmail.com> <87fugwsx2s.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49937) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d3jbU-00019V-EZ for guix-devel@gnu.org; Thu, 27 Apr 2017 09:37:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d3jbP-00087C-ET for guix-devel@gnu.org; Thu, 27 Apr 2017 09:37:04 -0400 In-Reply-To: <87fugwsx2s.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 25 Apr 2017 10:36:27 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel@gnu.org Hello! Ricardo Wurmus skribis: > Mekeor Melire writes: [...] >> And secondly, each user could have a user.scm e.g. like >> >> (user-configuration >> ; ... >> (aliases >> '( >> ("sysrec" "system reconfigure") >> ("pl" "pull") >> ; ... >> )) >> (services >> (emacs-daemon-service) >> (dzen-service) >> ; ... >> )) >> >> or similar :) > > While I=E2=80=99m not a fan of Guix-specific aliases, I think it=E2=80=99= s not a bad > idea to use Guix for user configurations. I=E2=80=99m tired of having to= keep > track of a set of custom configuration files scattered all over the > place, but I=E2=80=99m not sure how to approach this without going overbo= ard. > > To stay on the topic of user services: I think they do have a place in > Guix and could be defined with the same mechanisms that we have for > system services. Agreed. A =E2=80=98guix user=E2=80=99 tool (or similar) could talk to the = user=E2=80=99s Shepherd instance to upgrade user services like =E2=80=98upgrade-shepherd-services=E2=80=99 does in (guix scripts system). For non-Shepherd things, the benefits are less obvious to me. For instance, having ~/.bashrc be a simply to /gnu/store/=E2=80=A6-bashrc is not significantly better to having ~/.bashrc link to ~/directory-under-version-control/bashrc. Anyway, food for thought! Ludo=E2=80=99.