From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Allan Webber Subject: Guix on Debian (was: GSoC ideas) Date: Tue, 23 Feb 2016 15:52:30 -0800 Message-ID: <8737sj7znl.fsf@dustycloud.org> References: <20160206113802.GA17867@thebird.nl> <87mvre2eyz.fsf@gnu.org> <87wpqhu0t1.fsf@dustycloud.org> <20160208104530.GA26946@crashnator.suse.cz> <87zivbxggp.fsf@dustycloud.org> <87lh6vx9v0.fsf@dustycloud.org> <20160208204350.GA29053@thebird.nl> <1456268422.2159.23.camel@ghic.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34084) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYMkv-0004Fx-0V for guix-devel@gnu.org; Tue, 23 Feb 2016 18:52:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYMkq-0007il-WF for guix-devel@gnu.org; Tue, 23 Feb 2016 18:52:36 -0500 Received: from dustycloud.org ([50.116.34.160]:53068) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYMkq-0007ih-Rr for guix-devel@gnu.org; Tue, 23 Feb 2016 18:52:32 -0500 In-reply-to: <1456268422.2159.23.camel@ghic.org> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Diane Trout Cc: guix-devel Diane Trout writes: >> That looks like the way forward to me. Such a package can setup and >> start the daemon - which is enough. No need to get the blessing from >> the distributions themselves (will take time, but it will come - >> there >> really is no difference with allowing foreign packages to work >> anyway). > > > I wrote a basic Debian recipe to build guix, create the build users, > and install the systemd config file. > > https://github.com/detrout/debian-guix > > Currently I've only split the guix package into the emacs components > and everything else. I'd thought about splitting the daemon out into > its own package, but I wasn't sure what the daemon depended on. > > The daemon is still using the default /gnu/store path, and the user > needs to manually run guix authorize if they want to use hydra > binaries. The package is currently based on the stable 0.9.0 release, > and I'm not sure how security updates make it into a guix store if you > without updating the scheme packaging source tree. > > It might be nice to prompt the user if they wanted to authorize hydra > on install but that's not implemented. > > Currently its unlikely to go into Debian because Debian policy requires > everything to be built from source, and currently the Guix build > process downloads some bootstrap binaries. > > However with the current packaging "guix environment --pure bash -- > bash" does give me a clean guix environment, and the guix info docs get > installed when Debian emacs can see them. > > Diane Great work Diane! Are those bootstrapping binaries really necessary for getting Guix going? I guess for some reason I thought if you did the whole configure/make/etc dance it wouldn't be but maybe I'm wrong. Maybe this is a good step towards getting a Guix .deb we self-host on the Guix website? - Chris