From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Lepiller Subject: Re: about basic operation of guix sd Date: Wed, 15 Apr 2020 13:06:56 -0400 Message-ID: <540C0A88-4F2F-4CED-8C42-781820B314F1@lepiller.eu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40660) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jOlVW-0005gg-Bf for help-guix@gnu.org; Wed, 15 Apr 2020 13:07:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jOlVV-0002gp-5W for help-guix@gnu.org; Wed, 15 Apr 2020 13:07:26 -0400 Received: from lepiller.eu ([2a00:5884:8208::1]:51418) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jOlVU-0002dG-J6 for help-guix@gnu.org; Wed, 15 Apr 2020 13:07:25 -0400 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org, Satoru KURASHIKI Le 15 avril 2020 10:23:40 GMT-04:00, Satoru KURASHIKI = a =C3=A9crit : >hi, thank you for your reply=2E > >On Wed, Apr 8, 2020 at 1:30 AM Julien Lepiller >wrote: >> I think this is a bad idea, because it might break assumptions of the >mathematical model guix relies on=2E Not sure how to sync two stores >automatically=2E The "guix copy" command can be used to do that manually= =2E >Note that guix publish will publish your whole /gnu/store, >independently of how items were obtained=2E >> >> If you use guix publish for things that were not built on the >official build farm, you need to have a look at guix --archive to >generate key pairs and authorize your personal substitute server=2E For >items that were built on the official build farm, it is enough to >authorize the build farm, because these items will be detected as >identical, even if they come from a different source=2E > >Thanks, lazy evaluating "Invoking guix copy", it seems to be handy for >each target package! > >> The manual has a section "the perfect setup" that should explain >everything if you want to contribute=2E >> >> Guix pull is indeed more or less a wrapper around git pull=2E The >repository is available in the store, but because of the mathematical >model, it is read-only and must not be modified=2E You can still use >"guix edit foo" to open the package definition of foo in your favorite >editor=2E > >OK, I wil read that section throughly when time come=2E >For now I have to used to its daily administration=2E=2E=2E > >>> If this is not for a contribution, the next best thing you can do is >create a channel that allows you to share your modifications (or you >can keep them private, but share them between your computers)=2E >> >> Note that the guix-daemon is only there to build and download >packages, it doesn't know anything about available packages, etc=2E Your >guix command does=2E That allows each user on your system to customize >the set of available packages=2E > >Anyway, I use GUIX_PACKAGE_PATH and have managed to build small font >package recipe=2E >With some more, I will try it migrating to channel=2E GUIX_PACKAGE_PATH is the deprecated way to use a channel (introduced befor= e tge notion of channels)=2E If you have a working dehinition with it, you = can simply do "git init" and push it as a new repo somewhere=2E Then, set u= p your ~/=2Econfig/guix/channels=2Escm to use it=2E To test changes in your channel you can use "-L path/to/channel/root" (sam= e as what you pass to GUIX_PACKAGE_PATH) with any guix command=2E > >regards, >-- >KURASHIKI Satoru