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) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B23B7158089 for ; Sat, 23 Sep 2023 17:48:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B22AF2BC02F; Sat, 23 Sep 2023 17:48:54 +0000 (UTC) Received: from smtp.gentoo.org (dev.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 757482BC014 for ; Sat, 23 Sep 2023 17:48:54 +0000 (UTC) From: Ulrich Mueller To: Alex Boag-Munroe Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Standard parsable format for profiles/package.mask file In-Reply-To: (Alex Boag-Munroe's message of "Sat, 23 Sep 2023 15:01:57 +0100") References: <5b5dfbfd-9c7d-a26b-65e7-9f8c5e48bb8f@gentoo.org> <87msxfjix6.fsf@gentoo.org> <878r8yjohn.fsf@gentoo.org> <871qeqjmup.fsf@gentoo.org> Date: Sat, 23 Sep 2023 19:48:45 +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: 312bb111-486f-49a2-b4dd-3b620757564a X-Archives-Hash: 3ce9735284291ddf371d7c97a2a1a8e8 --=-=-= Content-Type: text/plain >>>>> On Sat, 23 Sep 2023, Alex Boag-Munroe wrote: > I'm confused, you're against adding "massive header blocks" but you're > fine with Arthur's 9 line entry but not my 8 line one. Your 8 line entry was this (please correct me if you meant to refer to an entry from a different message): --- 8< --- # [PREAMBLE] # Timestamp: 2023-09-21 15:07:42+00:00 # Author: Arthur Zamarin # Justification: Very broken, no idea why packaged, need to drop ASAP. # The project is done with supporting this package. # Bugs: 667687, 667689 # Packages: dev-lang/python dev-lang/python --- >8 --- And Arthur's was this: --- 8< --- # Arthur Zamarin (2023-09-21) # Very broken, no idea why packaged, need to drop ASAP. The project # is done with supporting this package. See for history bug #667889. # # As a better plan, you should migrate to dev-lang/perl, which has # better compatibility with dev-lang/ruby when used with dev-lang/lua # bindings. # Removal on 2023-10-21. Bug #667687, #667689. dev-lang/python --- >8 --- Of course it is longer when it contains 4 additional lines of explanation. > My idea was a stop gap to add something easily parsed once the > comments are stripped but keeping the comments in place currently for > backwards compatibility. Yes, understood. I think we should keep the "simple line-based file" format [1] with comments. If we would change it to something completely different, we would also impose that format on users' (public or private) overlays. Also, we'd either have to change the files in /etc/portage (not sure how popular that would be) or live with two different and incompatible formats in profiles and user configuration. Ulrich [1] https://projects.gentoo.org/pms/8/pms.html#x1-480005.2.5 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFDBAEBCAAtFiEEtDnZ1O9xIP68rzDbUYgzUIhBXi4FAmUPJP0PHHVsbUBnZW50 b28ub3JnAAoJEFGIM1CIQV4uNCEH/32eEnRhDlplGWkoD17/wHF/Fu/wVYTDc6Kb mWr6nYxGUQ+UdQwNIKdHMhtOlgZ2pLVK0tD0KQEPuFSx2ze4JNiEHBEjfaOgMx1R ZgRmnwezj0IwbrQFVoO870MSnDxv8/AlYfUj72FUrq7PUl35dnvQxE1n6JRvY9e9 9YlWY8l0lcMQurwO8Tf+Dtw9d8WGO9A2KRKzdEcYcbnE6sukDt4x4RwnmKhSPxM6 J39oXJF+ffd49q/XhcGWRfzqLi99yTjJXrF2GO8y/pPGuWSnRlILBPKsJmVTAbNy YKVYtQr2K04E6RKR1qvueWRS+2VFMc0H6WTm8IkPDunBrh2aZYo= =lNjE -----END PGP SIGNATURE----- --=-=-=--