From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, guile-user@gnu.org
Subject: Re: guix is the guildhall that we always wanted!
Date: Fri, 17 Mar 2017 13:32:27 +0100 [thread overview]
Message-ID: <87fuicm6ck.fsf@igalia.com> (raw)
In-Reply-To: <87a88kf8cu.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 17 Mar 2017 12:30:57 +0100")
On Fri 17 Mar 2017 12:30, ludo@gnu.org (Ludovic Courtès) writes:
>> 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?
No, I think the guildhall is simply another source of package
definitions for Guix. Pack creation would be done by the user as
needed -- if I want to ship packages A, B, and C, I can just do that.
Some of those packages might be defined in Guix proper and some from
guildhall.
The interesting bit I think is simply being able to add to the set of
guildhall packages in a decentralized way, to complement the set of
packages in core Guix. I imagine the package flow over time would be
from guildhall to core guix.
Andy
next prev parent reply other threads:[~2017-03-17 12:32 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
2017-03-17 12:32 ` Andy Wingo [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fuicm6ck.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.