Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id B7A1663237A for ; Tue, 6 Jul 2010 09:54:08 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 82281-05 for ; Tue, 6 Jul 2010 12:54:01 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mail.postgresql.org (Postfix) with ESMTP id 3D88F632198 for ; Tue, 6 Jul 2010 09:54:01 -0300 (ADT) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OW7ew-0005gr-Ml for pgsql-docs@postgresql.org; Tue, 06 Jul 2010 14:53:58 +0200 Received: from d222146.adsl.hansenet.de ([80.171.222.146]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Jul 2010 14:53:58 +0200 Received: from tim by d222146.adsl.hansenet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Jul 2010 14:53:58 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: pgsql-docs@postgresql.org To: pgsql-docs@postgresql.org From: Tim Landscheidt Subject: Re: "Localizing" paths? Date: Tue, 06 Jul 2010 12:53:45 +0000 Organization: Lines: 25 Message-ID: References: <1278349811-sup-6775@alvh.no-ip.org> <13257.1278374919@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: d222146.adsl.hansenet.de Mail-Copies-To: never User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:5A1ZzHoB57I+trAy0EbsuFR6KG4= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.51 tagged_above=-5 required=5 tests=BAYES_05=-0.5, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201007/57 X-Sequence-Number: 5713 Tom Lane wrote: >> Would it be feasible and desirable to "localize" the paths >> in the configure stage? Pro: Fewer guesses by new users. >> Con: Adds another level of complexity to the build system. > The bigger "con" is that anyone reading the docs on-line would be > given information that might be inappropriate for their platform. Why? That would only be the case if the on-line docs were copied verbatim from some developer's working directory (or a buildfarm box). I don't know the current workflow, but it shouldn't be a problem to "./configure --host=DOC-DUMMY && make www-install". The biggest con I see is with the generation. If I under- stood the discussion on the diagrams correctly, the tar balls for the packagers have the documentation already done, so the generation of the docs would either have to be pushed to a later stage, or the users of packages wouldn't have any benefit at all. So, looking at the pro: Shelved it. Tim