Jean-Marc Lasgouttes wrote:
> Angus> One more question. I've slotted this packaging stuff into LyX
> Angus> 1.3.x. All it does is set the paths in the package class. The
> Angus> rest of LyX uses the existing stuff. Running in-place I get
> Angus> this output:
> 
> The patch looks OK.

Any ideas about how to move the USE_FOO_PACKAGING stuff to the configure
script?

> Angus> Question. Should localedir be set unless I explicitly define
> Angus> the LYX_LOCALEDIR environment variable? It's being set above
> Angus> with the LOCALEDIR macro being passed to package.C by the
> Angus> compiler.
> 
> Could you rephrase the question please? I think I can parse it, but
> then I do not understand it...

Sure.

We have three tests to find the "localedir".
1. Use an environment variable, LYX_LOCALEDIR, to point us to it.
2. Try and guess localedir from the <path to executable>/../locale.
3. Fall back on the hard-coded LOCALEDIR macro that is passed to package.C
as a compiler flag.

If we run LyX in-place, then (2) fails. I'm suggesting that if LyX is run
in-place, then we shouldn't fall through to try (3) because it's an
'installed' location, not an 'in-place' one.

-- 
Angus

Reply via email to