From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24525 invoked by alias); 24 May 2003 09:52:01 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 24504 invoked from network); 24 May 2003 09:52:01 -0000 Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164) by sources.redhat.com with SMTP; 24 May 2003 09:52:01 -0000 Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.20) id 19JVh2-00032z-Q9 for gcc@gnu.org; Sat, 24 May 2003 05:52:00 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19JVgq-0003Dh-AJ for gcc@gnu.org; Sat, 24 May 2003 05:51:51 -0400 Received: from vexpert.dbai.tuwien.ac.at ([128.131.111.2]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19JVgY-0001yn-Ds for gcc@gnu.org; Sat, 24 May 2003 05:51:30 -0400 Received: from [128.131.111.60] (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id CCB761378D; Sat, 24 May 2003 11:51:27 +0200 (CEST) Date: Sat, 24 May 2003 11:21:00 -0000 From: Gerald Pfeifer To: phil@ipal.net Cc: gcc@gnu.org Subject: Re: downloading GCC documentation In-Reply-To: <20030508205616.GA1298@aludra> Message-ID: References: <20030508205616.GA1298@aludra> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-12.7 required=5.0 tests=DOMAIN_BODY,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, SIGNATURE_SHORT_DENSE,SPAM_PHRASE_01_02,USER_AGENT_PINE version=2.41 X-Spam-Level: X-SW-Source: 2003-05/txt/msg02185.txt.bz2 On Thu, 8 May 2003 phil@ipal.net wrote: > It would be nice if there was a link to allowing downloading the full > GCC documentation tree as a tar.gz file. I have looked on the following > pages and do not see such a link: I had a look, and you should be able to download that using rsync (http://gcc.gnu.org/rsync.html). > I want to read the documentation while "offline" (literally, while my > slow dialup modem is busy downloading the latest of everything, which is > usually the case 95% of the time) in my web browser. Alternatively, > "one big HTML file" could work, although I suspect that would be > unwieldy for something the scale of GCC. But I think the tar.gz thing > should be readily doable. This is one of those issues where you provide something (useful) and people keep asking for more and more and more. :-} Have you considered using the .info docs that we ship as part of releases (and which you can build yourself when bootstrapping GCC as well)? There are now nice info readers such as tkInfo, and thanks to a patch by Mike Stump, for future versions of GCC you'll be able to easily generate the HTML versions yourself by a simple `make html`. > Further, the web server on gcc.gnu.org does not give a Last-modified > header, so wget always retrieves each file all over again on each pass. I have reported this to the gcc.gnu.org admins. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/