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:31 +0900 [thread overview]
Message-ID: <CAM0xXk-gNn1Jt8kxP37+rj2NGFbnOKNMsrgxochLBEWn5hFEcQ@mail.gmail.com> (raw)
In-Reply-To: <87lfn7mfb4.fsf@devup.no>
hi, thank you for your reply.
On Wed, Apr 8, 2020 at 1:27 AM Marius Bakke <mbakke@fastmail.com> wrote:
>
> Hi Satoru, and welcome to Guix! I hope you will enjoy your stay. :-)
>
> Satoru KURASHIKI <lurdan@gmail.com> writes:
>
> > hi,
> >
> > I happen to know Guix SD recently, and trying to tinkering it.
>
> FYI the 'SD' name has been deprecated in favor of 'Guix System'.
Ah, I see, so there are several bindings...:)
> Syncing /gnu/store will not work without also syncing /var/guix/db. I
> think what you want to do is on host1 run 'guix publish' as you already
> found, and on host2 you can then use 'guix install foo
> --substitute-urls="https://host1 https://ci.guix.gnu.org"' to get
> substitutes from both host1 and the Guix CI infrastructure.
>
> See https://guix.gnu.org/manual/en/guix.html#Invoking-guix-publish for a
> more complete explanation.
>
hmm...OK, so it's dificult to have a partial mirror on my tiny VPS.
# I thought of pushing to VPS from my desktop, and fetch them from
# old laptop when I'm away from home. (to demonstrate guix to friends)
## mainly for iwlwifi things and so on. kernel demands me one night.
> To do this through the configuration system, you need
> 'guix-publish-service-type' and adjusting the 'substitute-urls' field of
> 'guix-service-type'.
>
> > - The right way of treating guix code (or guile code structure?)
> > - I have to clone guix repo into my home directory?
> > - Though "guix pull" should have source tree anywhere (in
> > /gnu/store?), so are there any interfaces
> > to access them through guix-daemon?
> > - I want to tweak existing code (package definition)
> > - I should copy target file to somewhere working directory to edit
> > or edit target file in the project tree?
>
> After cloning the Guix repository, you can run Guix directly from the
> checkout using the "./pre-inst-env" script: see the Contributing
> section of the manual for how to configure a development environment:
>
> https://guix.gnu.org/manual/en/guix.html#Contributing
>
> Another alternative is to use 'guix pull --url=/your/cloned/repository'.
Hacking guix itself is... difficult for me, so I expect guix command to work
out of the box:
- invoke "current" guix
- it refers current store (readonly), cloned checkout of guix tree (overriding
current one), and my local package module
would be desirable.
> You can get completion and jumping through Geiser, but I don't have
> instructions at hand. Hopefully some of the Emacs gurus can chime in
> here. :-)
I've found setting "geiser-guile-load-path" and Autodoc seems to work.
I will try to build environment on this.
regards,
--
KURASHIKI Satoru
next prev parent 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 [this message]
2020-04-07 16:30 ` Julien Lepiller
2020-04-15 14:23 ` Satoru KURASHIKI
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-gNn1Jt8kxP37+rj2NGFbnOKNMsrgxochLBEWn5hFEcQ@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).