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 5BC34158094 for ; Fri, 23 Sep 2022 14:04:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 88F78E0BE1; Fri, 23 Sep 2022 14:04:00 +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)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4CBF7E0BB1 for ; Fri, 23 Sep 2022 14:04:00 +0000 (UTC) From: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Cc: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= Subject: [gentoo-dev] [PATCH 0/3] glep-0074: clarifications about size and checksum fields Date: Fri, 23 Sep 2022 16:03:52 +0200 Message-Id: <20220923140355.1307514-1-mgorny@gentoo.org> X-Mailer: git-send-email 2.37.3 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: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: a77ea83c-200c-4248-a724-3822724b16b4 X-Archives-Hash: 971d8d6a9b67951f16c3e2e2cab224d5 Hi, Here's next part of GLEP 74 updates, this time I think it qualifiers as 100% editorial. Ulrich Müller noticed that we don't specify how to express sizes and checksums. I've partially solved the latter while adding the hash algorithm table and these patches should clarify the matters even further. Notably, they: 1) clarify that DIST entries are relevant to package managers only 2) specify that size is an unsigned decimal, and checksums consist of name-value pairs 3) clarify that 'Hex' encoding of hashes means lowercase hex without any prefix or suffix Perhaps the most controversial part is requiring lowercase -- but (drumroll...) Portage reports hash mismatch if you use uppercase. Michał Górny (3): glep-0074: Clarify that DIST entries are specific to PMs glep-0074: Specify the format of size and checksum fields glep-0074: Clarify the hex encoding of hash values glep-0074.rst | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) -- 2.37.3