From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: Re: On network management and documenting nmcli Date: Tue, 22 May 2018 14:42:19 +0200 Message-ID: <1d86d711-8917-effc-c1e1-0fc09d23c5c8@riseup.net> References: <87in7u33xy.fsf@gmail.com> <87y3goe16z.fsf@gmail.com> <871segm3iz.fsf@gmail.com> <8736yvzbzz.fsf@gmail.com> <87r2mfqs3j.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56889) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fL95j-0001Zh-SL for help-guix@gnu.org; Tue, 22 May 2018 11:20:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fL95f-0001Se-TD for help-guix@gnu.org; Tue, 22 May 2018 11:20:47 -0400 Received: from mx1.riseup.net ([198.252.153.129]:56619) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fL95f-0001SL-Kn for help-guix@gnu.org; Tue, 22 May 2018 11:20:43 -0400 Received: from cotinga.riseup.net (cotinga-pn.riseup.net [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 132C01A0C1C for ; Tue, 22 May 2018 08:20:42 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by cotinga.riseup.net with ESMTPSA id 82F2DAC3A6 for ; Tue, 22 May 2018 08:20:41 -0700 (PDT) In-Reply-To: <87r2mfqs3j.fsf@gmail.com> Content-Language: sv-FI List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org On 2018-05-13 21:21, Pierre Neidhardt wrote: > You are very true, and while the manual hints at > lightweight-desktop.scm, it does not go any further with respect to > giving an outlook of what to expect from it: which services, which > programs, etc. > > With little Scheme code the experienced users can investigate that by > themselves, but it's not quite obvious for newcomers. > > If not only for nmcli, I would suggest we document more those > pre-defined profiles for the sake of making GuixSD more approachable. I agree. Here we could choose between just listing them in the manual which=20 increases the work on updating the manual when we change the default=20 profiles or Giving the newcomers the means to see for themselves what=20 programs/services they contain. This should be done in a way that=20 explains more than the name of the service/package does. Perhaps a new guix command is needed for this e.g.: % guix show %default-services getty=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 | A service that serves tty cups=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0 | Printin= g service that enables printing ... For information about how to remove or add services see Services (info) i= n the manual. This command "guix show" could then be hinted at in the example=20 configuration files. --- Swedebugia