From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Overlays Date: Sat, 31 Aug 2013 17:57:59 +0200 Message-ID: <87k3j1ua2g.fsf@gnu.org> References: <87vc2o4qwc.fsf@gnu.org> <87eh9c9sb8.fsf@gnu.org> <20130830160948.GB5927@kubera.inria.fr> <87bo4f3ric.fsf_-_@gnu.org> <87hae6nc50.fsf@karetnikov.org> <878uzi27tw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42886) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFndv-0003me-A3 for guix-devel@gnu.org; Sat, 31 Aug 2013 12:03:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VFndn-0008Kj-Vi for guix-devel@gnu.org; Sat, 31 Aug 2013 12:03:19 -0400 Received: from hera.aquilenet.fr ([141.255.128.1]:57421) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VFndn-0008KV-Om for guix-devel@gnu.org; Sat, 31 Aug 2013 12:03:11 -0400 In-Reply-To: (Amirouche Boubekki's message of "Sat, 31 Aug 2013 12:56:15 +0200") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Amirouche Boubekki Cc: guix-devel@gnu.org Amirouche Boubekki skribis: > The issue I see is that some one wants to distribute recipes but > doesn't want to contribute them in the guix repository. One way to do > that is to fork the guix repository and merge once in a while and then > ask the users to install packages using the command used during > development from the forked repository. Otherwise, if overlays were > supported users would just have to install overlays somewhat like apt > sources and use the same command as with guix distribution recipes. Without touching the Guix code, Guix users can always create their own modules containing their own package recipes. For instance, in my-own.scm, one could write: (define-module (my-own) #:use-module (guix packages) ...) (define-public my-own-package (package (name "my-own") ...)) All the API is usable from there, in particular =E2=80=98package-derivation= =E2=80=99. >From the command-line, one can run: guix build -e '(@ (my-own) my-own-package)' or: guix package -e '(@ (my-own) my-own-package)' What does not work, though, is: guix package -i my-own So, to me, that=E2=80=99s what we=E2=80=99d want to fix. >> In Guix, third parties could distribute their own Guile modules that >> define packages. Guix would need a way to nicely deal with them at the >> command line, but otherwise it=E2=80=99s just Guile modules. > > IIRC in nixos one just has to use the command =C2=ABnix-env -i > path/to/nix/package=C2=BB to install a recipe out of nixpkg tree, I'm not > sure it's supported by guix. It is, see above. :-) > Anyway, the reason I raised now this feature is because: > > - I find it a useful feature, but the features you proposed for 0.4 > are way more interesting for the time being > - One user complained on IRC that overlays could *streamline* recipes > contributions that said contributing packages is not difficult using > the guix repository > > So what I propose is to put this feature request in a TODO to avoid > future loosly backed request like mine (except if someone wants to > work on this) and focus on the 0.4 roadmap :) Agreed! Thanks for explaining, Ludo=E2=80=99.