From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Extending Guix without using the Guile load path
Date: Wed, 19 Feb 2020 16:36:13 +0100
Message-ID: <87o8tulhci.fsf@elephly.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:60545)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <rekado@elephly.net>) id 1j4RP0-00037k-A3
 for guix-devel@gnu.org; Wed, 19 Feb 2020 10:37:01 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <rekado@elephly.net>) id 1j4ROg-0005nC-68
 for guix-devel@gnu.org; Wed, 19 Feb 2020 10:36:42 -0500
Received: from sender4-of-o51.zoho.com ([136.143.188.51]:21149)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <rekado@elephly.net>) id 1j4ROf-0005l2-O2
 for guix-devel@gnu.org; Wed, 19 Feb 2020 10:36:22 -0500
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: Guix-devel <guix-devel@gnu.org>

Hi Guix,

I think it=E2=80=99s a bit difficult to install the Guix Workflow Language =
at
this point and I=E2=80=99d like to change that.

Currently, new sub-commands for Guix are looked up by module name on the
Guile load path.  When installing the =E2=80=9Cgwl=E2=80=9D package, though=
, the Guile
load path is not automatically altered, so users need to set it up by
themselves.  The load path is only altered automatically when users
install the =E2=80=9Cguile=E2=80=9D package.  This is not a good recommenda=
tion because
users may have Guile 2.2 in their profile, and not Guile 3.0 or whatever
version may be needed by the extension.

I wonder if we can make this a little nicer by letting Guix look for
sub-command scripts in directories that are listed in an environment
variable, such as GUIX_EXTENSIONS_PATH.  The =E2=80=9Cguix=E2=80=9D package=
 would set
this search path and packages wanting to provide a sub-command (such as
=E2=80=9Cguix workflow=E2=80=9D or =E2=80=9Cguix home=E2=80=9D) would arran=
ge to have their scripts
placed in that sub-directory of their outputs.

What do you think?

--
Ricardo