From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.tsag.net (smtp2.tsag.net [208.118.68.91]) by sourceware.org (Postfix) with ESMTPS id 3D448385615C; Thu, 20 Oct 2022 11:55:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3D448385615C Authentication-Results: sourceware.org; dmarc=pass (p=quarantine dis=none) header.from=linuxfromscratch.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=linuxfromscratch.org Received: from linuxfromscratch.org (rivendell.linuxfromscratch.org [208.118.68.85]) (user=smtprelay@linuxfromscratch.org mech=PLAIN bits=0) by smtp2.tsag.net with ESMTP id 29KBt7EC005399-29KBt7EE005399 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 20 Oct 2022 05:55:07 -0600 Received: from localhost.localdomain (xry111.site [89.208.246.23]) by linuxfromscratch.org (Postfix) with ESMTPSA id EB2771C3424; Thu, 20 Oct 2022 11:55:04 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfromscratch.org; s=cert4; t=1666266907; bh=yIa8jB1vSFvd+GKxY6iGfY0OdpsDLEc4fwzTGYQXbJk=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=n/zpUKbCXjQdDRhupxwU4AoPyUV3JmG3py9m9EJiRY1lpI3DhPteZG+MS9xMNFMSc Qqo6qA3+We2WEDhPdL1mb1znOfpiyS6Fm/OePeJ5E+poMFakPhoVDWIsXTOYrMEyAR ohKo9vr2U9ulcwW8q9nffZ/ImlX8AguNuuCzBi1bCe/yyf7FrGOZzzyJ+Zu2/HKYTk MJsHLBpIhKurB25KrP/GzBXVfvJRffYDEZeB0YQpujz3EX5VkXMms9oN3RpPagr0x2 BqRmciLjkU8EB6w+vJJpa2m0PY1txTYXA3hfWqOjYgbKyzPzmniiDjk0oS8hOLDSyA zCgK2cAcs4XhQ== Message-ID: Subject: Re: Announcement: Porting the Docs to Sphinx - 9. November 2022 From: Xi Ruoyao To: Martin =?gb2312?Q?Li=810=948ka?= , GCC Patches , GCC Development Cc: Sandra Loosemore , "Joseph S. Myers" , Bruce Dubbs , Pierre Labastie , "Douglas R. Reno" Date: Thu, 20 Oct 2022 19:55:01 +0800 In-Reply-To: <1d5c952d-5101-3c53-dfde-df139f67d1b4@suse.cz> References: <9975b774-46d7-8870-fd92-498f5ec50ab4@suse.cz> <9ea57a95-fefe-81a3-848e-ede0893f5b61@suse.cz> <8198573b-89e2-a232-3e33-0e5c4153c112@suse.cz> <494cee6fc68c06e039f46c3d6f8331a32e81ab5e.camel@linuxfromscratch.org> <7bae16bc-9069-4964-a80e-7ebff82e007e@suse.cz> <1d5c952d-5101-3c53-dfde-df139f67d1b4@suse.cz> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.0 MIME-Version: 1.0 X-FEAS-Auth-User: smtprelay@linuxfromscratch.org X-FEAS-DKIM: Valid Authentication-Results: smtp2.tsag.net; dkim=pass header.i=@linuxfromscratch.org; dmarc=pass header.from=linuxfromscratch.org X-FE-Policy-ID: 0:14:3:linuxfromscratch.org X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Thu, 2022-10-20 at 13:53 +0200, Martin Li=C5=A1ka wrote: > On 10/20/22 13:49, Xi Ruoyao wrote: > > (CC our team members.) > >=20 > > On Thu, 2022-10-20 at 13:27 +0200, Martin Li=C5=A1ka wrote: > > > > Ouch.=C2=A0 This will be very painful for Linux From Scratch.=C2=A0= We'll need to > > > > add 23 Python modules to build the documentation, while we only hav= e 88 > > > > packages in total currently...=C2=A0 And we don't want to omit GCC > > > > documentation in our system. > > >=20 > > > Various other distros will have to face it too. The proper solution i= s a multi-build > > > package (gcc:doc) which can be built later in the dependency chain. B= tw. do you also > > > provide PDF documentation in your system? > >=20 > > No (texlive is much heavier than Sphinx).=C2=A0 But generally we expect= man > > pages and info pages. > >=20 > > We can separate man and info into the second-time build in BLFS (we're > > already doing this now for Go, Objective C, etc.), >=20 > Do the same for GCC. >=20 > > but I don't really > > like to omit the man and info pages.. >=20 > What should I do about it? We want to switch to a more modern documentati= on tool > called Sphinx and yes, it will make packaging of the GCC more complicated= . Nothing, I guess. We'll handle it on our side (if we finally decide to ship the man/info tarballs we can generate them by ourselves). I was just trying to find a simpler solution before beginning all the work :). Thanks!