From mboxrd@z Thu Jan 1 00:00:00 1970 From: Satoru KURASHIKI Subject: Re: about basic operation of guix sd Date: Wed, 15 Apr 2020 23:23:40 +0900 Message-ID: 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]:45655) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jOixG-0005l9-7z for help-guix@gnu.org; Wed, 15 Apr 2020 10:23:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jOixF-0003TQ-6I for help-guix@gnu.org; Wed, 15 Apr 2020 10:23:54 -0400 Received: from mail-yb1-xb32.google.com ([2607:f8b0:4864:20::b32]:42127) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jOixF-0003TE-2L for help-guix@gnu.org; Wed, 15 Apr 2020 10:23:53 -0400 Received: by mail-yb1-xb32.google.com with SMTP id c13so65267ybp.9 for ; Wed, 15 Apr 2020 07:23:53 -0700 (PDT) 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 hi, thank you for your reply. 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 mat= hematical model guix relies on. Not sure how to sync two stores automatical= ly. The "guix copy" command can be used to do that manually. Note that guix= publish will publish your whole /gnu/store, independently of how items wer= e obtained. > > If you use guix publish for things that were not built on the official bu= ild farm, you need to have a look at guix --archive to generate key pairs a= nd authorize your personal substitute server. 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 differe= nt source. 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 everythi= ng if you want to contribute. > > Guix pull is indeed more or less a wrapper around git pull. The repositor= y is available in the store, but because of the mathematical model, it is r= ead-only and must not be modified. You can still use "guix edit foo" to ope= n the package definition of foo in your favorite editor. OK, I wil read that section throughly when time come. For now I have to used to its daily administration... >> If this is not for a contribution, the next best thing you can do is cre= ate a channel that allows you to share your modifications (or you can keep = them private, but share them between your computers). > > Note that the guix-daemon is only there to build and download packages, i= t doesn't know anything about available packages, etc. Your guix command do= es. That allows each user on your system to customize the set of available = packages. Anyway, I use GUIX_PACKAGE_PATH and have managed to build small font package recipe. With some more, I will try it migrating to channel. regards, -- KURASHIKI Satoru