public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tim Landscheidt <[email protected]>
To: [email protected]
Subject: Re: "Localizing" paths?
Date: Tue, 06 Jul 2010 12:53:45 +0000
Message-ID: <[email protected]> (raw)
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Tom Lane <[email protected]> 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

view thread (14+ messages)  latest in thread

reply

Reply instructions:

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

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: "Localizing" paths?
  In-Reply-To: <[email protected]>

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

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox