From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 47D17158089 for ; Thu, 21 Sep 2023 21:22:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D26982BC0A6; Thu, 21 Sep 2023 21:22:36 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (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 87D5C2BC01C for ; Thu, 21 Sep 2023 21:22:36 +0000 (UTC) From: Ulrich Mueller To: Arthur Zamarin Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Standard parsable format for profiles/package.mask file In-Reply-To: (Arthur Zamarin's message of "Thu, 21 Sep 2023 22:40:05 +0300") References: Date: Thu, 21 Sep 2023 23:22:27 +0200 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail 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: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Archives-Salt: e2ecc6f8-b2f0-472a-b6fe-359404c41af3 X-Archives-Hash: e9a7109a53b9126a3dc72c4348edf2e4 --=-=-= Content-Type: text/plain >>>>> On Thu, 21 Sep 2023, Arthur Zamarin wrote: > ===== "Formal" format ===== > Each entry is composed of 2 parts: "#"-prefixed explanation block and > list of "${CATEGORY}/${PN}" packages. Entries are separated when a new > explanation block starts (meaning first "#"-prefixed line after packages > list). You may add newlines between packages in packages list. "Must" rather than "may" here? You certainly cannot list several packages in the same line. > The first line of the "#"-prefixed explanation block must be of the > format "${AUTHOR_NAME} <${EMAIL}> (${SINGLE_DATE})" when the date is of > format YYYY-MM-DD, in UTC timezone. > If this is a last-rite message, the last line must list the last-rite > last date (removal date) and the last-rite bug number. You can also list > other bugs relevant to the last-rite. So I think a format of: "Removal > on ${REMOVAL_DATE}. Bug #NNNNNN, #NNNNNN." Where the bug list is comma > and space separated, we have at least one space (" +" regex) between the > removal date and bug list, and the date is of YYYY-MM-DD format. > I prefer this line is separate (and not continuous of prefix message text). > The explanation block itself can reference bugs, by matching the regex > "[Bb]ugs? #\d+(, +#\d+)*" (For example: "bug #713106, #753134"). I think > this is quite a simple one, but powerful enough for most. > Lines with single newline between them (so no blank line between them) > are considered as single paragraph continuum. If you want to start new > paragraph, leave a blank line (still prefixed with #) - think similar to > markdown. A line matching the last-rite line is always it's own paragraph. Is this rule about paragraphs needed? It is at odds with the rule that the removal date and bug must be on their own line (i.e. that line is _not_ part of a "paragraph continuum"). What about the introductory comment block in the file? Should there be a defined syntax for a separator between it and the rest of the file? For example, everything above the first line matching "^#[ \t]*---" could be ignored by automatic tools, and they would insert new entries below that separator. > Should it be a GLEP, I don't think so? But I'm unsure about it. We do > need to document it (for example header of that exact file). It shouldn't be too difficult to wrap this up as a GLEP. OTOH, we don't have a GLEP for eclassdoc either. Ulrich --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFDBAEBCAAtFiEEtDnZ1O9xIP68rzDbUYgzUIhBXi4FAmUMtBMPHHVsbUBnZW50 b28ub3JnAAoJEFGIM1CIQV4uCsMIAMDpEHdBaNPHjHiwjr5EXGMdGxZsCl4AU7e3 TKk8lDAM3ZqyqfB5o9TpQXfUn+mOfzF0xEbmPn6fIUd1BYuQVf1FBGoBwWK7/XbA 4WGyVHu4gAyv8DSm3ZHrf3Xd3HMGrcFaKsyU65xmw9eR8ryAZI1JX1ezXAVG4Fsz svUyT3VIA6cs+1yJq0gnqQ/kOvGP26IWzgYQvOkrT/eDkwgBlFbKQjKbI9Z4Foxe JKDHGBnNiHACUNt15nRRa1cT/+g4gCX9ph7SSjE0DZhqfMJ4qwiNsstvjib2HYul wFrbZyzJzxbNbnNT+7804Fw+DF7YeLGUKPNZAJ3PSxxeUgXRnqs= =rL8j -----END PGP SIGNATURE----- --=-=-=--