On Wed, Apr 04, 2007 at 02:43:49PM -0400, Timothy Reaves wrote: > Let's take your example about a printer driver. When I want a new > printer driver, I download the driver, run the installer, and done. I > can use the new printer. By your example above, you imply directly that > the same can be done with TeX packages. So, where is the package I > download for nomencl, that when I double click on it it will install, > and all is well. Oh, wait a minute, such things don't exist! Your > analogy fails. Horribly.
That's not a LyX problem. Setting up a .msi that installs a few TeX files for a given, fixed TeX distribution is a matter of installing the WIX toolset and writing a 200 or so lines .wxs file. If this would be done, installing the TeX files would indeed be doubleclicking the .msi. .msi is btw the _native_ packaging format for Windows, so one would assume that every decent Windows developer would use it. This, of course, would be the responsibility of the _TeX distribution_, i.e. MikTeX. [Of course the question is why everybody keeps inventing installers on Windows. Obvious answer is that (a) nobody is really interested in package _management_, and (b) .msi is an overengineered clumsy-to-use, resource wasting machinery that breaks more often than not]. But in any case: None of this is LyX business. > Whereas a package manager may be nice, it's not really needed. > Why couldn't LyX users, who know what they're doing, bundle up sets of > styles (don't know the proper name for each type of TeX 'thing'), use > a cross-platform install product, and there you go. There is no cross-platform install product. And believe me, something that runs both on Win2k and WinXP is _not_ considered being cross-platform in some parts of the world. Andre'
