From: Leo Famulari <leo@famulari.name>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix on Debian (was: GSoC ideas)
Date: Tue, 23 Feb 2016 19:02:34 -0500 [thread overview]
Message-ID: <20160224000234.GA21278@jasmine> (raw)
In-Reply-To: <8737sj7znl.fsf@dustycloud.org>
On Tue, Feb 23, 2016 at 03:52:30PM -0800, Christopher Allan Webber wrote:
> Diane Trout writes:
>
> >> That looks like the way forward to me. Such a package can setup and
> >> start the daemon - which is enough. No need to get the blessing from
> >> the distributions themselves (will take time, but it will come -
> >> there
> >> really is no difference with allowing foreign packages to work
> >> anyway).
> >
> >
> > I wrote a basic Debian recipe to build guix, create the build users,
> > and install the systemd config file.
> >
> > https://github.com/detrout/debian-guix
> >
> > Currently I've only split the guix package into the emacs components
> > and everything else. I'd thought about splitting the daemon out into
> > its own package, but I wasn't sure what the daemon depended on.
> >
> > The daemon is still using the default /gnu/store path, and the user
> > needs to manually run guix authorize if they want to use hydra
> > binaries. The package is currently based on the stable 0.9.0 release,
> > and I'm not sure how security updates make it into a guix store if you
> > without updating the scheme packaging source tree.
> >
> > It might be nice to prompt the user if they wanted to authorize hydra
> > on install but that's not implemented.
> >
> > Currently its unlikely to go into Debian because Debian policy requires
> > everything to be built from source, and currently the Guix build
> > process downloads some bootstrap binaries.
> >
> > However with the current packaging "guix environment --pure bash --
> > bash" does give me a clean guix environment, and the guix info docs get
> > installed when Debian emacs can see them.
> >
> > Diane
>
> Great work Diane!
>
> Are those bootstrapping binaries really necessary for getting Guix
> going? I guess for some reason I thought if you did the whole
> configure/make/etc dance it wouldn't be but maybe I'm wrong.
My understanding is that if you alter the bootstrap binaries, the entire
dependency graph will change, forcing a rebuild of everything. And of
course, the altered binaries may present different interfaces, breaking
things as well.
next prev parent reply other threads:[~2016-02-24 0:02 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 11:38 GSoC ideas Pjotr Prins
2016-02-06 12:36 ` Ludovic Courtès
2016-02-06 18:54 ` Christopher Allan Webber
2016-02-07 10:16 ` Efraim Flashner
2016-02-09 20:52 ` Ludovic Courtès
2016-03-25 20:32 ` myglc2
2016-02-08 10:45 ` Tomáš Čech
2016-02-08 11:37 ` Efraim Flashner
2016-02-08 17:24 ` Christopher Allan Webber
2016-02-08 18:45 ` Thompson, David
2016-02-08 19:47 ` Christopher Allan Webber
2016-02-08 20:43 ` Pjotr Prins
2016-02-09 10:36 ` Installing Guix on foreign distros Ludovic Courtès
2016-02-10 8:53 ` Tomáš Čech
2016-02-10 9:42 ` Ricardo Wurmus
2016-02-10 12:44 ` Jookia
2016-02-11 5:44 ` Ricardo Wurmus
2016-02-11 10:54 ` Bootstrapping Ludovic Courtès
2016-02-23 23:00 ` GSoC ideas Diane Trout
2016-02-23 23:52 ` Guix on Debian (was: GSoC ideas) Christopher Allan Webber
2016-02-24 0:02 ` Leo Famulari [this message]
2016-02-24 9:03 ` Ricardo Wurmus
2016-02-24 9:16 ` Efraim Flashner
2016-02-24 9:36 ` Jookia
2016-02-25 18:15 ` Bootstrap binaries Ludovic Courtès
2016-02-25 20:26 ` Christopher Allan Webber
2016-02-26 23:19 ` Ludovic Courtès
2016-02-28 10:51 ` Jookia
2016-02-28 15:08 ` Ludovic Courtès
2016-02-28 15:10 ` Jookia
2016-02-29 5:22 ` Christopher Allan Webber
2016-02-29 10:01 ` Ludovic Courtès
2016-02-24 0:32 ` Guix on Debian (was: GSoC ideas) Diane Trout
2016-02-24 7:04 ` Pjotr Prins
2016-02-24 17:20 ` Thompson, David
2016-02-24 19:36 ` Diane Trout
2016-02-25 10:30 ` Efraim Flashner
2016-02-26 1:27 ` Diane Trout
2016-02-24 19:14 ` GSoC ideas Jan Nieuwenhuizen
2016-02-24 21:24 ` Jan Nieuwenhuizen
2016-02-24 21:56 ` Diane Trout
2016-02-25 18:10 ` Ludovic Courtès
2016-02-26 1:28 ` Diane Trout
2016-03-25 20:52 ` myglc2
2016-02-09 20:49 ` Ludovic Courtès
2016-02-09 22:17 ` Christopher Allan Webber
2016-02-10 6:12 ` Pjotr Prins
2016-02-11 2:11 ` Christopher Allan Webber
2016-02-11 10:01 ` Ludovic Courtès
2016-02-11 17:59 ` Christopher Allan Webber
2016-02-21 21:07 ` Ludovic Courtès
2016-03-23 19:07 ` myglc2
2016-02-11 11:46 ` Manolis Ragkousis
2016-02-11 17:32 ` Andreas Enge
2016-02-12 11:48 ` Alex Sassmannshausen
2016-02-11 17:36 ` Christopher Allan Webber
2016-02-28 22:12 ` Samuel Thibault
2016-02-28 23:33 ` Richard Braun
2016-03-02 10:09 ` Ludovic Courtès
2016-03-02 10:12 ` Samuel Thibault
2016-03-02 21:31 ` Ludovic Courtès
2016-03-02 22:06 ` Samuel Thibault
2016-03-21 12:09 ` [GSoC] Porting GuixSD to GNU Hurd draft Manolis Ragkousis
2016-03-22 0:49 ` Samuel Thibault
2016-03-23 13:40 ` Ludovic Courtès
2016-03-23 16:55 ` Justus Winter
2016-03-24 11:18 ` Manolis Ragkousis
2016-03-24 11:38 ` Justus Winter
2016-03-24 12:36 ` Manolis Ragkousis
2016-03-24 12:49 ` Justus Winter
2016-03-24 13:22 ` Ludovic Courtès
2016-03-24 13:55 ` Manolis Ragkousis
2016-03-24 14:30 ` Justus Winter
2016-03-04 15:09 ` GSoC ideas Manolis Ragkousis
2016-03-05 22:02 ` Ludovic Courtès
2016-02-06 23:53 ` Ben Woodcroft
2016-02-07 5:51 ` Pjotr Prins
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=20160224000234.GA21278@jasmine \
--to=leo@famulari.name \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@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 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).