unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: 白い熊 <help-guix_gnu.org@sumou.com>
To: help-guix@gnu.org
Subject: Guix packaging tutorial with hand holding
Date: Thu, 30 May 2019 07:41:14 +0200 (GMT+02:00)	[thread overview]
Message-ID: <443844029.1559193703837.eu.faircode.email@localhost> (raw)


Hi Guix:

I'd like to advance step-by-step in learning how to write package definitions with the eventual goal of contributing to Guix.

For this I'd like to ask if someone could help me and other Guix-hacking-packaging beginners with some hand holding — concrete though, with examples, so I could then proceed through trial and error.

I've tried to follow the Guix packaging tutorial guide [1]. I can build and install the sample my-hello package with the from-file approach.

Next, I'd like to build and install the sample my-libgit2 package. Here, however I can't proceed:

The tutorial is old so it mentions the “GUIX_PACKAGE_PATH” approach which is deprecated and recommends using Guix channels. In the Guix manual I see the way to add a channel to your Guix, now is there a way to use a local git directory? So that I could experiment locally — without right away going through syncing the local git with an online git repository? If not I'll guess I'll have to go through Github just to play with some intro stuff.

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?

Finally, are there some nice examples of using inheritance? I.e. I just want to add a compile option, or some dependency to some package — is there some example I can play with?

Many thanks for any help! :@)

[1] https://www.gnu.org/software/guix/blog/2018/a-packaging-tutorial-for-guix/

--
 Best regards / 宜しく御願い致します / S pozdravem / C уважением / Z poważaniem /
 Mit freundlichen Grüßen

白い熊

             reply	other threads:[~2019-05-30  5:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  5:41 白い熊 [this message]
2019-05-30  6:56 ` Guix packaging tutorial with hand holding Ricardo Wurmus
2019-06-01 22:20   ` 白い熊
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=443844029.1559193703837.eu.faircode.email@localhost \
    --to=help-guix_gnu.org@sumou.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).