From: 白い熊 <help-guix_gnu.org@sumou.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Guix packaging tutorial with hand holding
Date: Sun, 2 Jun 2019 00:20:48 +0200 (GMT+02:00) [thread overview]
Message-ID: <570864249.1559426863378.eu.faircode.email@localhost> (raw)
In-Reply-To: <8736kwl9bb.fsf@elephly.net>
Thu May 30 08:56:58 GMT+02:00 2019 Ricardo Wurmus :
> You don’t need Github or any other externally hosted repository. You
> can use a local git directory just fine.
So in the channel definition using a local directory what would the syntax be instead of the “(url…” bit?
> > Second, working on the Guix git checkout is recommended as the best
> > way. What is the way of working with Guix git checkout on a GuixSD
> > system? I.e. should I pull, build it — the git. Then what? Where to
> > run guix pull and guix package -u — in the git, leave the SD versions
> > un-updated?
>
> When working with the Guix source code in a git checkout you don’t
> generally use “guix pull”. Instead you use “./pre-inst-env guix” to
> have Guix act on the modified source code. Using the git checkout is
> how you can modify modules that are part of Guix, which is how you can
> create patches that we can apply to Guix, so that everybody benefits
> from your changes.
>
> If you want to keep using the git checkout as your primary installation
> of Guix you can do that too, but combined with “guix pull” it’s a little
> inconvenient.
So what would the recommended workflow be, with a git checkout on top of GuixSD?
— Only use “guix pull, guix package -u, and guix system reconfigure” for GuixSD for root to have the base system up-to-date?
— Don't use “guix pull” as regular user for GuixSD, but install user packages from the git?
— In git use “./configure --localstatedir=/var; make; make install”? Also “make install”?
— Then to install packages use “./pre-inst-env guix install”?
--
Best regards / 宜しく御願い致します / S pozdravem / C уважением / Z poważaniem /
Mit freundlichen Grüßen
白い熊
next prev parent reply other threads:[~2019-06-01 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 5:41 Guix packaging tutorial with hand holding 白い熊
2019-05-30 6:56 ` Ricardo Wurmus
2019-06-01 22:20 ` 白い熊 [this message]
2019-05-30 21:37 ` Björn Höfling
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=570864249.1559426863378.eu.faircode.email@localhost \
--to=help-guix_gnu.org@sumou.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).