unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Real-world example for channels?
Date: Sun, 27 Jan 2019 00:00:58 +0100	[thread overview]
Message-ID: <87munnt45x.fsf@elephly.net> (raw)
In-Reply-To: <29d3b7b9-6d96-e132-e59e-ec7a5ccdd2f1@crazy-compilers.com>


Hi Hartmut,

> I'm looking for some real-world examples for channels.

Here’s an example:

    https://github.com/BIMSBbioinfo/guix-bimsb

> After reading
> <https://www.gnu.org/software/guix/manual/en/html_node/Channels.html>
> I'm confused:
>
>   * AFAIU Section 3.7.1 shows an example for pulling *whole* guix from a
>     different location. So this needs to be a complete guix-clone
>     (optionally including my own package modules).

Correct.

>   * Section 3.7.2 describes how to add "a Git repository containing [my]
>     own package modules".
>       o What files or scm-packages is this git-repo expected to include?
>         What's the file-layout? Is there a suggested naming-convention?
>         How to #use-module these packages?

No files are expected to be included.  You only include files that you
want to offer.  There is no prescribed file layout, nor is there any
naming convention.

You #:use-module these modules like any other module.

If the repository contains a file “foo.scm” which starts with
“(define-module (foo) …)”, then you can “#:use-module (foo)” after the
repository has been added as a channel.

I suggest putting modules in separate namespaces.  All modules provided
by “guix-bimsb”, for example, are in the “bimsb” namespace.

--
Ricardo

  reply	other threads:[~2019-01-26 23:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 22:16 Real-world example for channels? Hartmut Goebel
2019-01-26 23:00 ` Ricardo Wurmus [this message]
2019-01-28  0:46   ` Chris Marusich
2019-01-28  6:57     ` Konrad Hinsen
2019-02-12 16:24     ` Ludovic Courtès
2019-02-13  5:41       ` Chris Marusich
2019-01-27  9:52 ` Efraim Flashner
2019-01-28  0:49 ` Chris Marusich

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=87munnt45x.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=h.goebel@crazy-compilers.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).