>> Automatic inclusion will be unlikely for any of the proposals because >> it is hard to tell which classes are standard latex packages that do >> not need to be included, and which ones are customized. Also, it is >> hard to include all needed .sty and other sort of dependent files. >> Some of these dependent files are even platform dependent. > > I suspected this was a problem...
.cls file sometimes load a bunch of .sty files and we need to detect them. I encountered the platform dependent case when a font is needed specifically for miktex/windows .... > I assume this in practice sometime results in an iteration where the > recipient complains that it doesn't compile because of this-and-that package > missing, followed by manually including a file, sending a new bundle and so > forth... A responsible sender would copy the file to another directory and try to compile, but I do agree that failure can happen. The point here is that with careful testing, one can give a new phd student a .lyx file and say, hey, this is our thesis template, just replace the parts and you are done. > It'd probably help if the user could specify where locally installed files > are found in his system. Then LyX might be able to automatically check for > files that come from those directories and that are needed. > > Is there currently a mechanism to "ask" LyX what files are used when > building a .lyx-file? Not that I am aware of. Some one might come up a good idea to probe all the needed files, I remembered that parsing latex log file could help. Bo
