unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: bug-guix@gnu.org, bug-hurd@gnu.org
Subject: Re: The Hurd, GNU, Guix, and GSoC
Date: Tue, 26 Mar 2013 21:41:48 +0100	[thread overview]
Message-ID: <871ub1yjub.fsf@gnu.org> (raw)
In-Reply-To: <5151FC7B.8010003@gmail.com> (Cyril Roelandt's message of "Tue, 26 Mar 2013 20:52:27 +0100")

Cyril Roelandt <tipecaml@gmail.com> skribis:

> On 03/26/2013 06:24 PM, Ludovic Courtès wrote:

[...]

>> The mission of GNU Guix [0] is to be a package manager for, and
>> distribution of, the GNU system.  The distribution only works on
>> GNU/Linux currently, but the goal is to support the Hurd (when it has
>> source releases...), and possibly kFreeBSD.
>>
>> Thus, it will most probably have to restrict itself to features provided
>> by all three kernels.  However, it could make use of Hurd-specific
>> features when running on it, such as unionfs.
>>
>
> This makes perfect sense. Since FreeBSD is way more popular than the
> Hurd, maybe students would be more likely to be willing to work on a
> Guix + (k)FreeBSD project. Do we know (k)FreeBSD people who might aslo
> be interested in Guix ? :p

Perhaps, but that’s off-topic.

>> GSoC-wise, possible projects include:
>>
>>    • porting the distribution to GNU/Hurd (but again, I’d rather rely on
>>      published source tarballs of the Hurd, libc, etc. than on Git
>>      checkouts);
>
> What's so wrong with git checkouts ? Are you afraid the code might not
> be very stable ?

No.  It’s just that, IMO, it’s the developers’ responsibility to
identify milestones in their project and to give it a version number.
Deferring that choice to people outside of the project may not be as
fruitful.

Ludo’.

  reply	other threads:[~2013-03-26 20:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 17:24 The Hurd, GNU, Guix, and GSoC Ludovic Courtès
2013-03-26 19:52 ` Cyril Roelandt
2013-03-26 20:41   ` Ludovic Courtès [this message]
2013-03-26 21:14 ` Arne Babenhauserheide
2013-03-29 18:18 ` 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=871ub1yjub.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=tipecaml@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).