unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Satoru KURASHIKI <lurdan@gmail.com>
To: help-guix@gnu.org
Subject: Re: about basic operation of guix sd
Date: Wed, 15 Apr 2020 23:23:40 +0900	[thread overview]
Message-ID: <CAM0xXk-5fUg3szE48gZ9doCVMfWp3oqP76BqoDde-R__Br+snw@mail.gmail.com> (raw)
In-Reply-To: <DD3D568D-A187-4FDF-8453-90A61C3BBA12@lepiller.eu>

hi, thank you for your reply.

On Wed, Apr 8, 2020 at 1:30 AM Julien Lepiller <julien@lepiller.eu> wrote:
> I think this is a bad idea, because it might break assumptions of the mathematical model guix relies on. Not sure how to sync two stores automatically. 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 were obtained.
>
> 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. 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.

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.
>
> Guix pull is indeed more or less a wrapper around git pull. The repository is available in the store, but because of the mathematical model, it is read-only and must not be modified. You can still use "guix edit foo" to open 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 create 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, it doesn't know anything about available packages, etc. Your guix command does. 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

  reply	other threads:[~2020-04-15 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 15:16 about basic operation of guix sd Satoru KURASHIKI
2020-04-07 16:27 ` Marius Bakke
2020-04-15 14:23   ` Satoru KURASHIKI
2020-04-07 16:30 ` Julien Lepiller
2020-04-15 14:23   ` Satoru KURASHIKI [this message]
2020-04-15 17:06     ` Julien Lepiller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM0xXk-5fUg3szE48gZ9doCVMfWp3oqP76BqoDde-R__Br+snw@mail.gmail.com \
    --to=lurdan@gmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).