From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id gEXABjB6kWNOUAEAbAwnHQ (envelope-from ) for ; Thu, 08 Dec 2022 06:46:24 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id uGyxBjB6kWOT0wAAauVa8A (envelope-from ) for ; Thu, 08 Dec 2022 06:46:24 +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 967872FCE9 for ; Thu, 8 Dec 2022 06:46:23 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p39jI-0002dO-9r; Thu, 08 Dec 2022 00:45:56 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p39j7-0002av-UA for guix-devel@gnu.org; Thu, 08 Dec 2022 00:45:54 -0500 Received: from cascadia.aikidev.net ([173.255.214.101]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p39j5-0003AJ-Dl for guix-devel@gnu.org; Thu, 08 Dec 2022 00:45:45 -0500 Received: from localhost (unknown [IPv6:2600:3c01:e000:21:7:77:0:20]) (Authenticated sender: vagrant@aikidev.net) by cascadia.aikidev.net (Postfix) with ESMTPSA id EAF651AB72; Wed, 7 Dec 2022 21:45:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=reproducible-builds.org; s=1.vagrant; t=1670478321; bh=3iRtNpfWLlnYvYxcoRPaT/K+dnnrWPQwhkQWDZuV3c4=; h=From:To:Subject:In-Reply-To:References:Date:From; b=R3UplJz42j4HGIIxYL6jqlKv5WkBqThz37J6Rc9oeATrCbQwN7vO+sfLAlPXVMk23 JCPTWEyAAT7IwzV6BrKLJbOnUQCs3m3JnZcmsn996USPmrQSLxQT9dROVBV+Z4jZyD jDbsciHVO1FadUdXTaq1zKMVQJCCZ5gPyKCwmtcbjT1NQiqKunfR3LqMPoKSbV10mz HFwoYL+xBqagTC2LkhhRwGUp3uwAyB6uhV7ICKf3lI4aPwdEhp9wNd53xzrUcIvarQ 8arIF2MJFoc3lqoXljrfQq6BUhplEQuiudkYURXrgH2ZqepTj+xf66xXHAxZeJ7r/3 FUPFXOMFppPbg== From: Vagrant Cascadian To: jgart , Guix Devel Subject: Re: Should a Guix package include documentation dependencies to be considered complete? In-Reply-To: <20221207191711.GB847@dismail.de> References: <20221207191711.GB847@dismail.de> Date: Wed, 07 Dec 2022 21:45:14 -0800 Message-ID: <87v8mmbg9h.fsf@contorta> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Received-SPF: pass client-ip=173.255.214.101; envelope-from=vagrant@reproducible-builds.org; helo=cascadia.aikidev.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham 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-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1670478383; 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=EMgXef1mr21muxZkpsrJdHXttI81I0/r2rj4HZAeiHM=; b=ZpQ/j522pdaMezCJoSPMx5LaT5riNKl6ku/i/Fi+CClBjGdCL6kTR1IWXkpY40UxG4FAZb UaPkst9gkG+TxOdiKBqxz3Mar0CdNr/WTzVCheXe/ViiriJANzUIQjs0mcPv2TUdhteu2p ItqBYqe3LPemBBPCRyGrWwuBLLv2TaVsJgYmXxxAXwHuWXj/nRBrxurSFIWxBfEEz6tjVw x0mVpgCQMd9myy1Ed+eqAC+T899KLuDVPzErbO1eqG6xRtOokDq30PzY6Ez+7NGrMOqSMv VJUWxXv3bRia85wuTOg6f4s+acwl5qEd4UoMHPvk3DJmAm7hhLIU/v5oThlLSg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1670478383; a=rsa-sha256; cv=none; b=uGfUKsUyvHvwr2Y5KmsSXpvYYtLByBFzbdTF4sd2u7FFV55YgOf+5u2bbaiKzalcEGo7JS Vtb/wtDyUbnUOnEtCJGh6iB1MLHOl7SS6bWLzuTFMzomz8HBDVfXhymhNYsVW4Z15EfAlg 2qNEsW5nLX+mcsYbjxIPCvp5mR6/eryVkWg11tkMSxYQUOZauUKnM2igdWKk9DbZYemE09 BA+K5TOVKNKCwBjeo6tKjsW7wx6jnSHn1VNPiyYqHTMQu4T6Yaba5c1uQAXQCUb7kwK4Re 7eckEun6gejArVgBD3DzzzHIySl0b9BPqZsaguzppULYcWz1zzqYOje0qv761w== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=reproducible-builds.org header.s=1.vagrant header.b=R3UplJz4; dmarc=none; 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: -4.06 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=reproducible-builds.org header.s=1.vagrant header.b=R3UplJz4; dmarc=none; 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: 967872FCE9 X-Spam-Score: -4.06 X-Migadu-Scanner: scn0.migadu.com X-TUID: E61CIeo4RgLw --=-=-= Content-Type: text/plain On 2022-12-07, jgart@dismail.de wrote: > We have abjad packaged but we don't necessarily have all the > dependencies needed to build everything that abjad provides such as a > PDF document that it mentions in its project Makefile. > > Should we include the LaTeX dependencies in the abjad package? > > Should all Python packages include the required dependencies to build documentation? With my Reproducible Builds hat on... Some of the main remaining reproducibility issues in Debian are with documentation generation, notably .pdf and various non-determinism issues in sphinx, frequently used to generate documentation in various formats in python projects. I would hate to have a policy to always generate documentation if it makes Guix less reproducible... maybe putting the documentation into a separate output at least? While unreproducible documentation is unfortunate, it is not that same as, say, the kernel or important core libraries. I personally have a strong preference for formats that are largely readable as "plain" text (markdown, restructuredtext) to fancy formatting; you can just copy them into the package rather than having to transform them into some fancy format. I also get that that does not work for everyone... > We currently include all the dependencies to run the tests, why not do > the same for documentation building? > > Should we make it a requirement or goal to always package a given package's "documentation-inputs"? Systematically and programatically being able to distinguish between "regular" inputs and test and documentation inputs sounds useful in a number off ways... my only worry would be when a particular input might shift from one category to another without noticing, and keeping track of those changes, and maybe cross building would be something to consider as well. But the advantages might outweigh the disadvantages. In Debian there is a concept of build profiles (e.g. nocheck, nodoc) which alter which dependencies are required to build the package. live well, vagrant --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCY5F57AAKCRDcUY/If5cW qmRwAQCcQdMHTdCkTKJghdSRORDNmX3S08QhlZZjdVijlFv1ggEA/qUXoAYPd1em 9viZlkTZsAj95gfHx93U2Hp9nxmJ6Qs= =JCI1 -----END PGP SIGNATURE----- --=-=-=--