Uwe Stöhr wrote: > Angus Leeming wrote: > >>>What other files are needed? >> >> That's precisely my point. I don't know. Off the top of my head: >> >> sed, tr, cut, grep... > > Looking at Ruurds Version, I know what is needed. I uploaded the files > as .rar to > > http://wiki.lyx.org/uploads/Tools/LyXWinTest/lyxutils.rar > > The files are the official actual versions. Taken from MSYS, Perl, and > Python. > > >> Isn't it possible to add an actual version of perl.exe, python.exe > >> and sh.exe (and some dll's if needed) to the folder LyX\bin\ and use > >> these files for lyxrc.defaults by default (as Ruurd did)? This > >> solution shouldn't produce NSIS troubles. > > > This solution will require > > 1. Extensive testing to ascertain which modules are needed by the > > scripts that LyX packages. > > Why extensive testing? We know which files are needed and provide the > official actual versions (the same that are used in the actual MSYS > version).
I'm afraid that I don't believe that this is so. Several scripts have changed since Ruurd released LyX/Win 1.3.5 and their requirements have changed too. Witness the reports that people have been making that the lyx2lyx packaged with tex2lyx doesn't work with Ruurd's python. > > 2. Ongoing maintenance. > > Only if some users have trouble. I remember only one problem since > LyXWin exists. I remember a whole stack of reports about missing python modules... > > Moreover, if I already have the "official" stuff installed why would I > > want to use the "unoffical" stuff? > > The files are the official ones. They are tested and under full support > of the authors. > > > Adding code to NSIS to conditionally install something is most > > certainly a "NSIS trouble" that I'm keen to avoid right now. > > I don't understand why this is an NSIS topic? I would just add the files > to the package and use them as default. Then you don't have to search > for the path to the files as they are part of the LyXWin package. Because I don't believe that Ruurd's stripped down versions are sufficient and I'm not willing to create *and test* their replacement. > > Would you prefer to use these stripped down things that people > > have been discovering don't work (see countleess reports on the > > lyx-users list), or would you prefer to use an official version which > > definitely will work but which requires a big download committment. > > The "countless" reports concerned a problem with a sed.exe version. Not really. It was a problem with the DOS line endings of the generated chkconfig.sed. But other scripts have problems too. > I installed your LyXWin version using the stripped files (I previously > deinstalled python, perl, and MSYS) and it works correctly. Ha! Scripts are by their nature dynamic. Have you tested that every single script works? Of course not! > OK I have not much time to test it roughly but I think it's stable. > There is now only one problem: > > If I use the stripped files, the folder of the files (if you include > them to your package it is then LyX's \bin folder) must be in the PATH. > But that could easily be fixed. ??? Then tell the installer where to find this folder and it'll add it to the path_prefix variable in lyxrc.defaults. -- Angus
