From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: new manifest format readers? Date: Fri, 09 Jun 2017 15:56:45 +0200 Message-ID: <87zidhl0wy.fsf@gnu.org> References: <87zidhcqr9.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42148) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dJKPD-0001KF-Rg for guix-devel@gnu.org; Fri, 09 Jun 2017 09:56:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dJKP9-0007V5-Qk for guix-devel@gnu.org; Fri, 09 Jun 2017 09:56:51 -0400 In-Reply-To: <87zidhcqr9.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 09 Jun 2017 14:03:22 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel Hi, Ricardo Wurmus skribis: > Can we simplify this case by adding manifest readers for different > formats? One simple format could be plain text: > > # this is for compilers > gfortran@5 > gcc-toolchain@5 > > # this is for fun > cdogs-sdl > > The manifest reader would just discard # comments and interpret each > non-empty line as a spec string. Sounds reasonable. I guess we=E2=80=99d need to add a new option to read this format, or should =E2=80=98guix package -m=E2=80=99 try to automatically dispatch based on th= e file name extension with a new --format option to override the guess? > While I love Scheme, I don=E2=80=99t think anything is to be gained from > exposing users who don=E2=80=99t want to use Scheme for manifests to opaq= ue > blobs of code and syntax they don=E2=80=99t want to understand. I thought everyone needed their dose of parentheses, but maybe you=E2=80=99= re right. :-) Ludo=E2=80=99.