From: ludo@gnu.org (Ludovic Courtès)
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 25296@debbugs.gnu.org, Mathieu Lirzin <mthl@gnu.org>
Subject: bug#25296: fully functional desktop installation
Date: Tue, 16 Jan 2018 14:57:09 +0100 [thread overview]
Message-ID: <87inc17vpm.fsf@gnu.org> (raw)
In-Reply-To: <a0b0cc59-5228-9409-9cc3-a1a467a9033d@fastmail.net> (Konrad Hinsen's message of "Tue, 16 Jan 2018 12:34:17 +0100")
Hi Konrad,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
>> Hmm, OK. Do you think it’s too much to ask, given the current audience
>> (tinkerers), to add those packages to their config, or to install them
>> with “guix package -i”?
>>
>> Admittedly this is a very subjective issue.
>
> How about organizing Guix in a layered way, with the core distribution
> containing narrow-purpose packages (mostly one piece of software), and
> another layer (in a distinct module, perhaps with a distinct naming
> convention) containing collections of software that works well
> together or is useful for a specific application domain? I see other
> use cases than just desktop stuff.
In GuixSD, that’s more or less what happens with ‘gnome-service-type’
and ‘xfce-service-type’, for example. (I’m not sure how that could work
at the Guix level, nor whether this is necessary.)
Ludo’.
next prev parent reply other threads:[~2018-01-16 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 22:10 bug#25296: fully functional desktop installation Quiliro
2017-01-02 21:11 ` Ludovic Courtès
[not found] ` <20170108041145.6d9a5cbc@riseup.net>
2017-01-08 10:16 ` Ludovic Courtès
2017-01-09 11:11 ` Ricardo Wurmus
2018-01-14 13:34 ` Mathieu Lirzin
2018-01-14 21:53 ` Ludovic Courtès
2018-01-15 13:26 ` Mathieu Lirzin
2018-01-15 13:49 ` myglc2
2018-01-16 10:31 ` Ludovic Courtès
2018-01-16 11:09 ` Danny Milosavljevic
2018-01-16 13:59 ` Ludovic Courtès
2018-01-17 7:09 ` Chris Marusich
2018-01-17 8:48 ` Ludovic Courtès
2018-01-16 11:34 ` Konrad Hinsen
2018-01-16 13:57 ` Ludovic Courtès [this message]
2018-01-16 15:40 ` Mathieu Lirzin
2018-01-17 9:56 ` Oleg Pykhalov
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=87inc17vpm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25296@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=mthl@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).