From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix libification.
Date: Sun, 11 Jun 2017 16:24:42 +0200 [thread overview]
Message-ID: <87efuqsitx.fsf@gnu.org> (raw)
In-Reply-To: <87a85gnoiy.fsf@gmail.com> (Mathieu Othacehe's message of "Sat, 10 Jun 2017 12:08:21 +0200")
Hello!
Mathieu Othacehe <m.othacehe@gmail.com> skribis:
> The script is becoming bigger and some parts of Guix would be really
> handy : (guix records), (guix workers), (guix utils) ...
>
> I don't want Guix to become a dependency of my script but copying parts
> of Guix in not great either. So I'm wondering if some parts of Guix,
> useful to other guile projects could be integrated to a lib, guile-lib
> for instance ?
I think it would be great, though there’s some friction: modules still
in flux are better kept in Guix proper because we can change them as we
see fit; modules that have become stable could be externalized, provided
someone steps up to maintain them and make frequent releases.
Recently Chris Webber integrated (guix hash) and (guix pk-crypto) into a
broader guile-gcrypt library, which I think is a good thing: this part
was stable enough and it’s definitely better to have one guile-gcrypt
project that everyone can build upon. Guix will use it once there’s
been a release or two I think. :-)
For smaller modules like records, workers, utils, I would suggest
integrating them into Guile proper or Guile-Lib maybe.
WDYT?
Ludo’.
next prev parent reply other threads:[~2017-06-11 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 10:08 Guix libification Mathieu Othacehe
2017-06-10 14:42 ` Mike Gerwitz
2017-06-10 16:04 ` Alex Kost
2017-06-10 16:32 ` Adam Van Ymeren
2017-06-11 7:19 ` Alex Vong
2017-06-12 16:53 ` Alex Kost
2017-06-11 14:24 ` Ludovic Courtès [this message]
2017-06-11 17:56 ` Jan Nieuwenhuizen
2017-06-11 20:22 ` Ludovic Courtès
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=87efuqsitx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=m.othacehe@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).