Stefan Schimanski wrote:
The Windows installer is in development/Win32/packaging. So is there
anything against putting it to development/MacOSX/packaging/installer ?
Nothing at all: that's what I'm asking for! (I don't have svn
privileges, so I can't do it myself, and even if I did I'd need to ask
permission anyway!)
But I am wondering what this installer is doing in fact. Why is copying
the LyX.app not enough?
It does three things.
1. Delete obsolete files. These are from pre-1.3.4: some math fonts
that got installed into ~/Library/Fonts/, and a Start-LyX.app that got
installed in /Applications/.
2. Managing the LyX User's folder so that users can use different
versions of LyX simultaneously and yet be able (for the most part) to
keep their past settings. So the installer copies ~/Library/Application
Support/LyX[-1.4] to ~/Library/Application Support/LyX-1.5, and then
modifies some lines in the preferences file to point to the new folder.
It also copies LyX's default templates from inside the application
bundle (where they are invisible) to .../LyX-1.5/templates/defaults.
3. Installing extra LaTeX class/style files that are good to have with
LyX -- such as preview.sty, srcltx.sty, and everything in
LyX.app/Contents/Resources/tex. All this gets copied (now) to
~/Library/texmf/tex/latex/lyx, and then texhash is run.
(1) we can probably dispense with now, especially if users are nervous
about having the installer delete things.
It would be nice to have a better solution for (3) as is true for linux:
buttons in file dialogs that take you straight to the default or user's
templates. It would be good as well to have something similar for LyX's
default example files, which are currently invisible to Mac users.
I'm not sure how better to handle (2).
If possible, I'd like to be able simply to copy the LyX.app and do it
without a separate installer. But again I don't know how to handle that.
Bennett
