public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106899] New: Snapshots do not contain pre-generated man pages & info pages
Date: Sat, 10 Sep 2022 02:54:53 +0000	[thread overview]
Message-ID: <bug-106899-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899

            Bug ID: 106899
           Summary: Snapshots do not contain pre-generated man pages &
                    info pages
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sam at gentoo dot org
  Target Milestone: ---

Would it be possible for the weekly snapshots to include pre-generated .info
pages (and man pages)?

Full releases do:
```
# find . | grep -i "\.info$"
./gcc-11.3.0/libquadmath/libquadmath.info
./gcc-11.3.0/libgomp/libgomp.info
./gcc-11.3.0/libitm/libitm.info
./gcc-11.3.0/gcc/fortran/gfortran.info
./gcc-11.3.0/gcc/doc/gccinstall.info
./gcc-11.3.0/gcc/doc/gccint.info
./gcc-11.3.0/gcc/doc/cpp.info
./gcc-11.3.0/gcc/doc/cppinternals.info
./gcc-11.3.0/gcc/doc/gcc.info
```

But snapshots don't:
```
/var/tmp/portage/sys-devel/gcc-11.3.1_p20220909/work # find . | grep -i
"\.info$"
/var/tmp/portage/sys-devel/gcc-11.3.1_p20220909/work #
```

             reply	other threads:[~2022-09-10  2:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10  2:54 sam at gentoo dot org [this message]
2022-09-10  3:00 ` [Bug other/106899] " pinskia at gcc dot gnu.org
2022-09-10  3:06 ` pinskia at gcc dot gnu.org
2022-09-10  3:15 ` sam at gentoo dot org
2022-09-10  3:43 ` pinskia at gcc dot gnu.org
2022-09-12  7:46 ` rguenth at gcc dot gnu.org
2023-08-19 20:19 ` mark at gcc dot gnu.org
2024-04-11  1:17 ` [Bug other/106899] Snapshots maybe should " pinskia at gcc dot gnu.org

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=bug-106899-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).