From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Real-world example for channels? Date: Tue, 12 Feb 2019 17:24:05 +0100 Message-ID: <87o97hht5m.fsf@gnu.org> References: <29d3b7b9-6d96-e132-e59e-ec7a5ccdd2f1@crazy-compilers.com> <87munnt45x.fsf@elephly.net> <87r2cxa9t6.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:35800) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtb2l-0005UT-5y for help-guix@gnu.org; Tue, 12 Feb 2019 11:36:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtaqx-0007FJ-46 for help-guix@gnu.org; Tue, 12 Feb 2019 11:24:12 -0500 Received: from hera.aquilenet.fr ([2a0c:e300::1]:58804) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gtaqw-0007Ag-Ob for help-guix@gnu.org; Tue, 12 Feb 2019 11:24:11 -0500 In-Reply-To: <87r2cxa9t6.fsf@gmail.com> (Chris Marusich's message of "Sun, 27 Jan 2019 16:46:13 -0800") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Chris Marusich Cc: help-guix Hi Chris, Chris Marusich skribis: > From d382cbddd11e86bd9b69f271782d2dccba180a05 Mon Sep 17 00:00:00 2001 > From: Chris Marusich > Date: Sun, 27 Jan 2019 16:29:30 -0800 > Subject: [PATCH] doc: Clarify channel file structure. > > Suggested by Hartmut Goebel . > > * doc/guix.texi (Channels): Clarify how a channel author should structure= the > files in their channel's Git repository. > --- > doc/guix.texi | 18 ++++++++++++++---- > 1 file changed, 14 insertions(+), 4 deletions(-) > > diff --git a/doc/guix.texi b/doc/guix.texi > index 22fc03b8f..5499ebf5b 100644 > --- a/doc/guix.texi > +++ b/doc/guix.texi > @@ -3691,10 +3691,20 @@ share your improvements, which are basic tenets of > email us at @email{guix-devel@@gnu.org} if you'd like to discuss this. > @end quotation >=20=20 > -Once you have a Git repository containing your own package modules, you = can > -write @code{~/.config/guix/channels.scm} to instruct @command{guix pull}= to > -pull from your personal channel @emph{in addition} to the default Guix > -channel(s): > +To create a channel, create a Git repository containing your own package > +modules and make it available. The repository can contain anything, but= a > +useful channel will contain Guile modules that export packages. Once you > +start using a channel, Guix will behave as if the root directory of that > +channel's Git repository has been added to the Guile load path (@pxref{L= oad > +Paths,,, guile, GNU Guile Reference Manual}). For example, if your chan= nel > +contains a file at @file{my-packages/my-tools.scm} that defines a Guile > +module, then the module will be available under the name @code{(my-packa= ges > +my-tools)}, and you will be able to use it like any other module > +(@pxref{Modules,,, guile, GNU Guile Reference Manual}). > + > +To use a channel, you can write @code{~/.config/guix/channels.scm} to in= struct > +@command{guix pull} to pull from your personal channel @emph{in addition= } to > +the default Guix channel(s): I=E2=80=99d perhaps move the =E2=80=9CTo create a channel=E2=80=9D paragrap= h after the =E2=80=9CTo use a channel=E2=80=9D paragraph, but otherwise LGTM. Thanks for taking the time to improve the manual! Ludo=E2=80=99.