On Jul 11, 2005, at 8:44 AM, Jean-Marc Lasgouttes wrote:
"Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> PACKAGE is hardcoded in config.h. Eg "lyx" or "lyx-1.3.6cvs".
Angus> If people specify PACKAGE as something other than "lyx", then
Angus> shouldn't their choice be respected?
Respect? What's that?
The idea was to change that into LyX or LyX-1.3.6cvs.
Angus> I don't know how important this is. Basically, I'm just
Angus> thinking out aloud...
I do not know either. But I guess you have a point.
What about the following patches (pick one)? What about windows?
JMarc
<lyxosx2.diff><lyxosx-config2.diff>
lyxosx2.diff works just fine as far as creating and using the
~/Library/Application Support/LyX directory.
lyxosx-config2.diff doesn't seem to do anything different: both the
user directory and binary within the application bundle come out as
"lyx". (Yes, I did run autogen.sh.)
I'm not sure if there's a reason to want to change (or want not to
change) the binary name. HFS+ (the Mac OS X standard) is case
insensitive but case preserving, so either "lyx" or "LyX" work. On a
UFS volume (supported on the Mac), it matters, of course, and I'm not
sure what happens when the LyX.app is opened from a UFS volume, whether
the binary needs to be "LyX" or "lyx".
Theoretically, the binary gets specified in the CFBundleExecutable
field of the Info.plist file contained in the application bundle. But
my experience is that this doesn't work reliably: when I add the
version suffix to lyx-1.4.0cvs, I can't simply get by with changing
CFBundleExecutable, but must add a link from lyx to lyx-1.4.0cvs.
Since I haven't heard of any complaints from users not being able to
use LyX/Mac on UFS, perhaps we ought to leave well enough alone with
the binary name.
Bennett
