On 10/20/22 13:49, Xi Ruoyao wrote: > (CC our team members.) > > On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote: >>> Ouch. This will be very painful for Linux From Scratch. We'll need to >>> add 23 Python modules to build the documentation, while we only have 88 >>> packages in total currently... And we don't want to omit GCC >>> documentation in our system. >> >> Various other distros will have to face it too. The proper solution is a >> multi-build >> package (gcc:doc) which can be built later in the dependency chain. Btw. do >> you also >> provide PDF documentation in your system? > > No (texlive is much heavier than Sphinx). But generally we expect man > pages and info pages. > > We can separate man and info into the second-time build in BLFS (we're > already doing this now for Go, Objective C, etc.),
Do the same for GCC. > but I don't really > like to omit the man and info pages.. What should I do about it? We want to switch to a more modern documentation tool called Sphinx and yes, it will make packaging of the GCC more complicated. Martin > >>> Could generated man and info pages be provided as a tarball on >>> gcc.gnu.org or ftp.gnu.org? >> >> Not planning doing that.
