public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@linuxfromscratch.org>
To: "Martin Li�0�8ka" <mliska@suse.cz>,
	"GCC Patches" <gcc-patches@gcc.gnu.org>,
	"GCC Development" <gcc@gcc.gnu.org>
Cc: Sandra Loosemore <sandra@codesourcery.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	Bruce Dubbs <bdubbs@linuxfromscratch.org>,
	Pierre Labastie <pierre.labastie@neuf.fr>,
	"Douglas R. Reno" <renodr2002@gmail.com>
Subject: Re: Announcement: Porting the Docs to Sphinx - 9. November 2022
Date: Thu, 20 Oct 2022 19:55:01 +0800	[thread overview]
Message-ID: <e385821eb18bf98098b2e00fc34db7a852aea9a0.camel@linuxfromscratch.org> (raw)
In-Reply-To: <1d5c952d-5101-3c53-dfde-df139f67d1b4@suse.cz>

On Thu, 2022-10-20 at 13:53 +0200, Martin Liška wrote:
> 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.

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!


  reply	other threads:[~2022-10-20 11:55 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 14:06 Porting the Docs to Sphinx - project status Martin Liška
2022-02-04 13:40 ` Matthias Klose
2022-03-08 15:59   ` Martin Liška
2022-08-02 12:48 ` Martin Liška
2022-10-17 13:28   ` Announcement: Porting the Docs to Sphinx - 9. November 2022 Martin Liška
2022-10-17 14:16     ` Paul Iannetta
2022-10-19  7:24       ` Martin Liška
2022-10-19  8:13         ` Paul Iannetta
2022-10-19  9:22           ` Martin Liška
2022-10-19 16:42             ` Joseph Myers
2022-10-20 11:13               ` Martin Liška
2022-10-17 22:26     ` Sandra Loosemore
2022-10-19 11:09       ` Martin Liška
2022-10-19 12:45         ` Martin Liška
2022-10-19 16:30         ` Sandra Loosemore
2022-10-20 11:26           ` Martin Liška
2022-10-20  2:26     ` Xi Ruoyao
2022-10-20 11:27       ` Martin Liška
2022-10-20 11:49         ` Xi Ruoyao
2022-10-20 11:53           ` Martin Liška
2022-10-20 11:55             ` Xi Ruoyao [this message]
2022-10-20 12:26               ` Martin Liška
2022-10-20 15:35         ` Joseph Myers
2022-10-20 15:50           ` Martin Liška
2022-10-20 16:43             ` Joseph Myers
2022-10-20 16:47               ` Jakub Jelinek
2022-11-08 13:55                 ` Announcement: Porting the Docs to Sphinx - tomorrow Martin Liška
2022-11-08 18:44                   ` Sam James
2022-11-09  0:00                     ` Joseph Myers
2022-11-09  0:06                       ` Sam James
2022-11-09  7:49                         ` Richard Biener
2022-11-09 10:18                           ` Mark Wielaard
2022-11-09 17:11                           ` Joseph Myers
2022-11-09 17:16                             ` Richard Biener
2022-11-11 20:52                   ` Gerald Pfeifer
2022-11-11 21:10                     ` Sandra Loosemore
2022-11-13 15:44                       ` Martin Liška
2022-11-09 14:45               ` Announcement: Porting the Docs to Sphinx - 9. November 2022 Martin Liška
2022-11-09 17:14                 ` Joseph Myers
2022-11-10 13:05                   ` Martin Liška
2022-11-10 13:50                     ` Richard Biener
2022-11-11 23:05     ` David Malcolm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e385821eb18bf98098b2e00fc34db7a852aea9a0.camel@linuxfromscratch.org \
    --to=xry111@linuxfromscratch.org \
    --cc=bdubbs@linuxfromscratch.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=mliska@suse.cz \
    --cc=pierre.labastie@neuf.fr \
    --cc=renodr2002@gmail.com \
    --cc=sandra@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).