unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guix-devel@gnu.org, guile-user@gnu.org
Subject: Re: guix is the guildhall that we always wanted!
Date: Fri, 17 Mar 2017 12:30:57 +0100	[thread overview]
Message-ID: <87a88kf8cu.fsf@gnu.org> (raw)
In-Reply-To: <87zigl3wph.fsf@pobox.com> (Andy Wingo's message of "Thu, 16 Mar 2017 19:25:46 +0100")

Hello!

Andy Wingo <wingo@pobox.com> skribis:

> Crucially, this "guix pack" is really an SDK for Guile and Fibers.
> Fibers is a library.  You can now make an SDK for anything!!!!!!!!!!!  I
> mean, I know, that's a lot of exclamation marks, but check it: you can
> develop locally, say using
>
>   /opt/guile-fibers-1.0.0/bin/guile -L /path/to/my/code
>
> and it just works.  If you package up your code, you can make a Guix
> package out of it and make a "guix pack" out of that closure and
> distribute it to your users: REGARDLESS OF WHAT OPERATING SYSTEM THEY
> RUN, AND WITH FULL SOURCE REPRODUCIBILITY.  It's huge.

IT’S AWESOME!!!!  ;-)

> But while getting your package into guix is easier than you think, it's
> not automatic.  I think there's room for a middle ground that's a bit
> more decentralized than Guix, but more centralized than people using
> GUIX_PACKAGE_PATH to add random directories of Guix package files.
>
> So!  My proposal for this new "guildhall" would be:
>
>     1. a web service
>
>     2. on which users registers projects
>
>     3. a project is a name + a git repository with a /package.scm file
>
>     4. the package.scm contains Guix package definitions for that project
>
>     5. the web service administers a git repository collecting those
>        packages
>        - without any hydra.gnu.org overhead
>        - without any manual checks
>        - in a form that you can just check out once and add to GUIX_PACKAGE_PATH
>
>     6. adding a new tag to a project's git repo of the form vX makes a
>        release X and updates the guildhall package
>        - it could be the web service has to poll git repos
>        - or maybe you have to invoke some command to update guildhall
>
>     7. probably we need to steal many ideas from npm.org

So are you suggesting that the new guildhall would provide
Guix-generated packs for those who don’t use Guix, and otherwise regular
Guix packages?

> Open questions would be, what about other targets like macOS or Windows
> or whatever?  There I don't know.  I suspect that if Guix becomes
> popular enough, someone will make a thing whereby you can cross-compile
> to macOS from GNU/Linux at least.  I know you can do that already with
> MinGW.  As for native "guildhall" operation on these targets, I don't
> know.  But I think that is a cost that people will pay for in time.

We could surely create cross-compiled packs for MinGW, though I suspect
a number of packages do not support cross-compilation.

Thanks for starting this thread!

Ludo’.

  parent reply	other threads:[~2017-03-17 11:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 18:25 guix is the guildhall that we always wanted! Andy Wingo
2017-03-16 19:26 ` Amirouche Boubekki
2017-03-17  8:23   ` Andy Wingo
2017-03-18  0:10     ` Arne Babenhauserheide
2017-03-16 22:01 ` Mark H Weaver
2017-03-16 22:24   ` Ludovic Courtès
2017-03-17  9:01     ` Florian Paul Schmidt
2017-03-17  9:45       ` Andy Wingo
2017-03-17 11:24       ` Ludovic Courtès
2017-03-17  6:51   ` Marko Rauhamaa
2017-03-17  8:30   ` Andy Wingo
2017-03-17 13:54     ` Christopher Allan Webber
2017-03-17 14:26       ` Andy Wingo
2017-03-18 14:00         ` Ludovic Courtès
2017-03-17 11:30 ` Ludovic Courtès [this message]
2017-03-17 12:32   ` Andy Wingo
2017-03-17 17:39     ` Pjotr Prins
2017-03-17 18:16       ` Mike Gran
2017-03-17 13:22   ` Eli Zaretskii
2017-03-18 14:04     ` Ludovic Courtès
2017-03-18 14:10       ` Eli Zaretskii
2017-03-19 15:57         ` Ludovic Courtès
2017-03-19 16:22           ` Eli Zaretskii

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=87a88kf8cu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=wingo@pobox.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).