From: Christopher Allan Webber <cwebber@dustycloud.org>
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 08:54:12 -0500 [thread overview]
Message-ID: <87lgs480vv.fsf@dustycloud.org> (raw)
In-Reply-To: <87efxwnw3x.fsf@igalia.com>
Andy Wingo writes:
> On Thu 16 Mar 2017 23:01, Mark H Weaver <mhw@netris.org> writes:
>
>> If [Guix] starts encouraging a decentralized approach, that would
>> result in strong pressure on us to freeze our API, which includes even
>> such details as which module each package is exported from. This
>> would drastically reduce the freedom Guix has to evolve the way its
>> packages are specified.
>
> I get what you are saying. I think that if a future guildhall is
> decentralized but uses Guix it needs to minimize its burden on Guix.
> That could mean that the packages are actually specified in a different
> DSL with different stability characteristics -- for example that DSL
> could call specification->package under the hood for example, like
> Ludovic mentions. (I should mention that this idea of using Guix and
> especially all its errors are my own -- haven't talked to others about
> it yet!)
>
> Which module a package definition is in is a good example of something
> not to depend on.
This makes sense to me... if it really is true that our scheme'y
Guildhall-style packages are so simple they're more data than code,
maybe we could even restrict them to... just data. Just a list of what
files are being provided, etc. That could easily be stored in some
minimal database.
I guess I'm saying +1.
next prev parent reply other threads:[~2017-03-17 13:54 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 [this message]
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
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=87lgs480vv.fsf@dustycloud.org \
--to=cwebber@dustycloud.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 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.