From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-100565-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 025D6158089
	for <garchives@archives.gentoo.org>; Fri, 22 Sep 2023 14:37:10 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 7806A2BC044;
	Fri, 22 Sep 2023 14:37:06 +0000 (UTC)
Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 45FEB2BC013
	for <gentoo-dev@lists.gentoo.org>; Fri, 22 Sep 2023 14:37:06 +0000 (UTC)
References: <b2a2515f-8c1e-4422-8cec-cd4fe3a4727c@gentoo.org>
 <5b5dfbfd-9c7d-a26b-65e7-9f8c5e48bb8f@gentoo.org> <ufs37i4z2@gentoo.org>
 <87msxfjix6.fsf@gentoo.org>
 <e2d4e8a5-2032-5e29-a9d4-04e553ec38bf@gentoo.org> <uv8c2h76o@gentoo.org>
 <w6glecy8lyr.fsf@uni-mainz.de> <878r8yjohn.fsf@gentoo.org>
 <CANvbShoC7UXd3xsN5sw0cuL6QNdMCE63uaRsPjy8NMzqNCy2_Q@mail.gmail.com>
User-agent: mu4e 1.10.6; emacs 30.0.50
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Standard parsable format for
 profiles/package.mask file
Date: Fri, 22 Sep 2023 15:36:03 +0100
Organization: Gentoo
In-reply-to: <CANvbShoC7UXd3xsN5sw0cuL6QNdMCE63uaRsPjy8NMzqNCy2_Q@mail.gmail.com>
Message-ID: <871qeqjmup.fsf@gentoo.org>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
Content-Type: text/plain
X-Archives-Salt: f9129b74-7856-49ec-9a28-ebdb9fe6cc40
X-Archives-Hash: 8272e02af128f2faa34bd68077a0ce59


Alex Boag-Munroe <ninpo@qap.la> writes:

> Any reason for the parseable parts to not be in an established human
> readable/editable format? e.g. the config ini style format, or TOML?

The only issue really is that depending on how it's done (do we do
it for the whole file, or just comments), it may need a new (profile)
EAPI which will take a while to implement and deploy.

If it's just for comments, then we can do it immediately though.

>
> To crib from the OP example with something configparser understands:
> [PREAMBLE]
> Timestamp: 2023-09-21 15:07:42+00:00
> Author: Arthur Zamarin <arthurzam@gentoo.org>
> Justification: Very broken, no idea why packaged, need to drop ASAP.
>     The project is done with supporting this package.
> Bugs: 667687, 667689
> Removal Date: 2023-10-21
> Packages: dev-lang/python
>
> The format is well documented already and simple to check for
> validity, so any GLEP would just need to cover correct keys/values.
>

But yeah, I agree it's worth thinking about a proper format rather than
fragile text mangling going into the future.

> Just a thought.