From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id sOp6OtubNWJSfQEAgWs5BA (envelope-from ) for ; Sat, 19 Mar 2022 10:01:15 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id WJvoN9ubNWIbzgAA9RJhRA (envelope-from ) for ; Sat, 19 Mar 2022 10:01:15 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 78BAE96B2 for ; Sat, 19 Mar 2022 10:01:15 +0100 (CET) Received: from localhost ([::1]:34570 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nVUxW-0001WV-KS for larch@yhetil.org; Sat, 19 Mar 2022 05:01:14 -0400 Received: from eggs.gnu.org ([209.51.188.92]:54912) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nVUwz-0001Vb-Dh for guix-devel@gnu.org; Sat, 19 Mar 2022 05:00:41 -0400 Received: from [2a02:1800:120:4::f00:13] (port=53218 helo=baptiste.telenet-ops.be) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nVUwx-000383-D6 for guix-devel@gnu.org; Sat, 19 Mar 2022 05:00:41 -0400 Received: from ptr-bvsjgyhxw7psv60dyze.18120a2.ip6.access.telenet.be ([IPv6:2a02:1811:8c09:9d00:3c5f:2eff:feb0:ba5a]) by baptiste.telenet-ops.be with bizsmtp id 890a270034UW6Th0190al3; Sat, 19 Mar 2022 10:00:34 +0100 Message-ID: Subject: Re: Fetching sources using Guix (re: Building a software toolchain that works) From: Maxime Devos To: Ryan Prior , Guix Devel Date: Sat, 19 Mar 2022 10:00:33 +0100 In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-PUtYR3FT3SzVArnPY+4E" User-Agent: Evolution 3.38.3-1 MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telenet.be; s=r22; t=1647680434; bh=pV03DiLevkSX58nHY6UTrgM0Giqq2VNM5afsnLvnQjk=; h=Subject:From:To:Date:In-Reply-To:References; b=KvWgFpYwBeEWzrECKoeH0GpwlUXfP5IGUvkOao6QYp7gD8+sj094VgVCXMsovqas9 CySTDicHGtX4gEcqvptYyroBEbefSjjlN0x7X0Ay21q7jGB+QMIP0seP5s4390iFCG I/ZQRyUWyjwbNlvrRXRC6xlnwdu1nfkXfNOLRVUauteYpDsmGT2zfSiR9YG8arr5dm Mi7itTyf6Mb5dTkThD1d7qeCW4Y1MGTxAYJb86RqdHkB00S0dTM/pIqRfAQ7ugYojO +UV76JL2wNuXk1qtOjJwu46IUMCMU1RsLV/zq0UydNhwq3v+IUGLkqQscV4A7CKadG Fk6EHez2W0biQ== X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a02:1800:120:4::f00:13 (failed) Received-SPF: pass client-ip=2a02:1800:120:4::f00:13; envelope-from=maximedevos@telenet.be; helo=baptiste.telenet-ops.be X-Spam_score_int: -19 X-Spam_score: -2.0 X-Spam_bar: -- X-Spam_report: (-2.0 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list 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+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1647680475; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=pV03DiLevkSX58nHY6UTrgM0Giqq2VNM5afsnLvnQjk=; b=T/G48hU/q2+vbOc9huROnJj6urrwIBW2COUl2pbWKvne5uw/k7oxpTEh9E/BRw2k4FcJP6 w2yqm2kyCd9bXdFPCnBCp1gVwp8mPnOKfjS5rSHQxZPED/ZGV6GQfA6bIQhp6BVn8RIybz MrRaAxYxMZ0i5UUefnIrzuW1B9yVVsXL/LIcdq5MxXZdc3rmgeru0t+ffqDsuXlAnM/KYI qY6T8LHxBIp1MvvEZtlIbGpjKBpGfzZAevcpMzYboKzX6cXtIq4AK8jG9I4OiU8wFCc3GW yhMe9FhtmyQpBTphXCpr2z791+cgfiHzHci+t4ZzK2ZcJhyq1RKYMwTZ/r2uhA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1647680475; a=rsa-sha256; cv=none; b=tIWORlU0ZFwqcst12lU/GDFfELTj4Ymz0FFDKNRqGpoYyNTA/AfT/fcOzcBDbQ/fLSpr1l rWyNXCbXy9urrzlkOvvRGWlbgXmZnpkm2YWVVNIlnXQUZPy0roI4AsLPcvx4laiggI4roA Van/FFqZkSYAtZS5/ZjFgHikQgufz8jXm35z7zTxsIEctdpDwudetUZAySKVnFqvTLJYGw NMf9f+yjp3ILaYhQ80bsRgsC5aic+L0gOnHRXNf6dI1McjBlXm8Q3DthBBIQkETitaf2Sd a7JzwvCNwBViYHeQL73RBnobTC0ISFsntnxCOFhCevQ6CABFWrFSSJU57omwpg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=telenet.be header.s=r22 header.b=KvWgFpYw; dmarc=pass (policy=none) header.from=telenet.be; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -6.34 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=telenet.be header.s=r22 header.b=KvWgFpYw; dmarc=pass (policy=none) header.from=telenet.be; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 78BAE96B2 X-Spam-Score: -6.34 X-Migadu-Scanner: scn1.migadu.com X-TUID: hrA1VDeasFBP --=-PUtYR3FT3SzVArnPY+4E Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ryan Prior schreef op za 19-03-2022 om 00:08 [+0000]: > Would it be feasible or desirable to create a set of "reason" > symbols, similar to our "licenses," and attach a reason (or unknown?) > to each snippet and patch? Then we can expose meaningful data to the > end-user about patches & snippets that are available, enabling an > informed choice about whether to apply them when fetching sources. >=20 > This could also be useful in our own record-keeping, so that we can > track the usage of patches and snippets for different reasons. It > would be nice, for example, to see a downward trend in the number of > patches for build systems that won't work at all without them, either > because we improve the logic in our build steps or because we > contribute changes upstream to make software easier to build. FWIW, when reviewing, I try to make sure that the reason is documented in a comment: (origin (snippet #~(begin ;; Remove bundled libraries (delete-file-recursively "vendor") ;; Remove non-free extension (delete-file-recursively "foobar")))) Additionally, patch files should contain a description what they are for and a link to the upstream record. So in theory, what you are describing is already being done, except it is done as comments and not some machine-readable tagging system. Greetings, Maxime. --=-PUtYR3FT3SzVArnPY+4E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iI0EABYKADUWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCYjWbsRccbWF4aW1lZGV2 b3NAdGVsZW5ldC5iZQAKCRBJ4+4iGRcl7m1JAP9j2sVB2Nc9uPdJWD3S+nYe1fEi voU4SGKyt7Y0mYOBJQD/UQL1e3X7LL7DHjD9rVYjPUpUdmUE3bsZiklJkX5HCQs= =1PiT -----END PGP SIGNATURE----- --=-PUtYR3FT3SzVArnPY+4E--