Re: "Localizing" paths?

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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