From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: bug#25296: fully functional desktop installation Date: Tue, 16 Jan 2018 12:34:17 +0100 Message-ID: References: <20161229171045.263747a9@riseup.net> <87bmvpb21m.fsf@gnu.org> <87a7xgwom7.fsf@gnu.org> <87shb8jedn.fsf@gnu.org> <87lggzdzh9.fsf@gnu.org> <87vag2857m.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58363) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ebPWF-0006O7-Gq for bug-guix@gnu.org; Tue, 16 Jan 2018 06:35:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ebPW9-0005MW-W4 for bug-guix@gnu.org; Tue, 16 Jan 2018 06:35:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:50232) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ebPW9-0005MO-TF for bug-guix@gnu.org; Tue, 16 Jan 2018 06:35:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ebPW9-0003HK-KH for bug-guix@gnu.org; Tue, 16 Jan 2018 06:35:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87vag2857m.fsf@gnu.org> Content-Language: en-US List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Mathieu Lirzin Cc: 25296@debbugs.gnu.org Hi, > 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. The main rationale for distinct layers is that assembling software at different levels requires different competences and different ways of documenting the assemblies. In the long run, I'd expect different people to be in charge of each layer. Konrad.