From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id SJmCBbVR7GR7ogAAG6o9tA:P1 (envelope-from ) for ; Mon, 28 Aug 2023 09:50:13 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id SJmCBbVR7GR7ogAAG6o9tA (envelope-from ) for ; Mon, 28 Aug 2023 09:50:13 +0200 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 B29D0384B6 for ; Mon, 28 Aug 2023 09:50:12 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=beffara.org header.s=gm1 header.b=DSdOPdmK; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1693209013; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=Un390NRMVmXFAQQPA8a9PjF+bQE/U/n1+sF2l302T0s=; b=p3nPwFfSvt8LV3RqXU7JP5eN10Hd72fKzbJyDvC/D0OpoJITlSOeuJT5U7ECr5pQ3Mehse 5ASevLJVPHVsKGysS4AOlpXD4R91XOUxCjlUzJfkU6YlozqLM8V0gKxXbZIOA3S8ctQmxI SJmKILlx0gGEnBK68FO0S3rn32cmCEZsGvmymTRRy2xTR60WInksDimcYYU/113o9Xaj38 ZflTnztW1HQSh0InTCinUH1AhlADgRTcZPCUVtgAdB6qafNeDnA66Yy3NSFkbaOJmpWTIU WdUt9Ze2FZvNM8QTF+KPyLLX30RKWEr2dVxY9nRyYF5w62/OAcqJ0kkJbgPj5Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=beffara.org header.s=gm1 header.b=DSdOPdmK; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1693209013; a=rsa-sha256; cv=none; b=AwD8ZCAI3xwCqQpbtrgkb/7ehDBiwTPC0WthJn0HEr6zYoq7AhZThUnPyEDDL+dcAdmAAX 2F6xqPp60GWJUQU0qcb7V6uSZczPBeIBO1L+MqB3Ug9WU/fEkkEmTjnjMtlrlZtqxtaLyG jn5kzQm24BXNB7ZN4erpx3/QVI9IXrLhgDeklXVyl3k/QgU4MYC0WJ5U4Z3z33lFnZOIzW PvCjq15w3V4UDoTK+jjy5SiuFt1ZKC3OzKRUQMSvEARJeapT6kh90oNqTmY45yMS4yyxO5 AenRRvoZEl6xbnRoOicMxvru43X4E+3qYV0yDiVTdjsdbBZ9dRRztYpyMa2rnw== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qaX0I-0005yd-0l; Mon, 28 Aug 2023 03:49:42 -0400 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 1qaX0C-0005yB-B7; Mon, 28 Aug 2023 03:49:38 -0400 Received: from relay2-d.mail.gandi.net ([2001:4b98:dc4:8::222]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qaX08-0006Nd-90; Mon, 28 Aug 2023 03:49:34 -0400 Received: by mail.gandi.net (Postfix) with ESMTPSA id 841C840004; Mon, 28 Aug 2023 07:49:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beffara.org; s=gm1; t=1693208966; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Un390NRMVmXFAQQPA8a9PjF+bQE/U/n1+sF2l302T0s=; b=DSdOPdmKCjBxMUtaokzCgzsKXN9I1izkoGWu0XD4e6TDjh2ELKz16/6ZwcdXWu8Jp8734l 0zP4cwj26c4l5WD2oetI9CXF52tWWQtspApgiwo5w2HkY8kFTnomkNwR1qATCA9Ep6o3uW JpdCzLMz4i+lrXj5dTVJWwIrCUqSrYY//f1iVjPkboa2jsPjLCTH4Q1ySA4L0KK3/atyBu mzvZnEJ9RzgZkSBWefV4/8si9678oeAjeHogDBAbwDoP3VwonCCA7+npYnJDq1supaSH67 pzRmjkOw4KWvKk+j/7hKn65Z3fpBm4FIxbZLP9H6Fnl8IsEmu4p0eW/4+stj0Q== Date: Mon, 28 Aug 2023 09:49:24 +0200 Message-ID: <20230828094924.GB1032@beffara.org> From: Emmanuel Beffara To: Nicolas Goaziou Cc: help-guix@gnu.org, guix-devel Subject: Re: documentation in TeX Live collections In-Reply-To: <87bkesrdx0.fsf@nicolasgoaziou.fr> References: <20230825121743.GD1356@beffara.org> <87bkesrdx0.fsf@nicolasgoaziou.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-GND-Sasl: manu@beffara.org Received-SPF: none client-ip=2001:4b98:dc4:8::222; envelope-from=manu@beffara.org; helo=relay2-d.mail.gandi.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx2.migadu.com X-Migadu-Spam-Score: -7.02 X-Spam-Score: -7.02 X-Migadu-Queue-Id: B29D0384B6 X-TUID: L11JQB45bWAF Hello, De Nicolas Goaziou le 27/08/2023 à 12:13: > > Apparently, all individual packages have a specific "doc" output but > > collections and schemes do not and they don't have them as inputs either. So > > we end up with an installation with no documentation > > It sounds like a good default to me. I doubt anyone reads all > documentation for every TeX Live package they install. Yet, as far as I know, most packages in Guix (apart from texlive-* ones) come with their documentation, so it feels somewhat inconsistent. But I agree that not including the docs in the main outputs can make sense, especially given the volume it represents. Anyway, given that there is extensive documentation in TeX Live, it seems only natural to have it easily accessible. > > I tried to explicity include documentation in a sub-shell but this changes > > nothing: > > > > $ guix shell texlive-latex:doc -- texdoc inputenc > > Note that you also need to install texlive-texdoc (or some collection/scheme including it). Indeed, but this command was run in a profile where texlive-scheme-medium is present, so texdoc was already available. Adding texlive-texdoc to the guix shell command does not change anything. > > Apparently the fact that this GUIX_TEXMF variable contains several paths is > > problematic for texdoc. > > Would the following definition for texlive-texdoc solve both issues > mentioned above? (the warning and the error.) [...] > (add-after 'link-scripts 'wrap-programs > (lambda _ > (wrap-program (string-append #$output "/bin/texdoc") > '("GUIX_TEXMF" = ("${GUIX_TEXMF%:*}")))))))) It would certainly remove the warning but it would make only the first path usable by texdoc, while other tools seem to support having several paths in GUIX_TEXMF. Besides, I don't understand how GUIX_TEXMF is taken into account by the various tools. Web2c and co don't know them, so there must be some wrapping or patching somewhere in the package definitions? > > Apparently something has triggered the download of documentation for all > > packages `texlive-scheme-medium` depends on but only the one I explicitly > > requested is made available in the profile (which is expected). All these > > other documentation were downloaded but not used and `guix gc` actually > > deletes them all! > > I noticed that, too, but I don't have any explanation for it at the > moment. Is there a way to diagnose that kind of thing? I stumbled on a similar behaviour in other contexts and was unable to investigate it (in my case, big debug versions of Qt libraries are often downloaded, although I neved requested any debugging version of anything). > > So what would be the proper way to install `texlive-scheme-medium` in a home > > profile with the documentation of the packages it includes ? > > If that's a common request, we could add a `texlive-collection-foo-doc' > package that would propagate all "doc" outputs from all packages > included in `texlive-collection-foo'. > > However, I'm a bit reluctant to add more artificial packages (i.e., not > known to TeX Live distribution). Also, it might be as simple to do it in > one's own manifest. I think it would make much more sense to have "doc" outputs also for collections and schemes. It would be consistent with the structure of individual packages and would not require artificial packages. Having individual package documentations in one's manifests is of course doable but it is contradictory with the approach of collections. -- Emmanuel Beffara