From: "Ludovic Courtès" <ludo@gnu.org>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: guix-devel@gnu.org
Subject: Re: GNU Guix & GuixSD 0.16.0 released
Date: Sat, 15 Dec 2018 19:03:44 +0100 [thread overview]
Message-ID: <87y38qy8e7.fsf@gnu.org> (raw)
In-Reply-To: <87sgz0fb3f.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Fri, 14 Dec 2018 15:15:48 +0100")
Hello,
Giovanni Biscuolo <g@xelera.eu> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Pjotr Prins <pjotr.public12@thebird.nl> skribis:
>>
>>> Yesterday I gave a passionate 'I love Guix' lightning talk about Guix
>>> packages at the biohackathon in Japan. Many people after approached me
>>> and said that the website is confusing them because it looks like it
>>> is promoting a Linux distribution... I know this is an old topic, but
>>> it would be nice if we found a way to promote Guix packaging as it
>>> works so well outside GuixSD.
>>
>> Yes, that should be a nice side-effect of calling everything “Guix”.
>
> does this mean that "guix system" is capable of
> instantiating/reconfiguring an operating-system declaration (services
> included) even outside GuixSD?
>
> AFAIK for this we need Sheperd as PID 1 and I do not know how I can get
> it on a systemd based (or any other different PID 1) distro
The only thing that doesn’t work on a foreign distro is ‘guix system
reconfigure’, understandably. The rest works exactly the same way.
Ludo’.
next prev parent reply other threads:[~2018-12-15 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 17:09 GNU Guix & GuixSD 0.16.0 released Ludovic Courtès
2018-12-06 17:23 ` Pierre Neidhardt
2018-12-07 7:06 ` Tobias Geerinckx-Rice
2018-12-07 12:20 ` Pjotr Prins
2018-12-07 11:07 ` L p R n d n
2018-12-10 4:02 ` Pjotr Prins
2018-12-14 10:20 ` Ludovic Courtès
2018-12-14 14:15 ` Giovanni Biscuolo
2018-12-15 18:03 ` Ludovic Courtès [this message]
2018-12-16 10:06 ` Ricardo Wurmus
2018-12-16 12:42 ` Giovanni Biscuolo
2018-12-16 14:11 ` George Clemmer
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=87y38qy8e7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=g@xelera.eu \
--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).