Le 12/04/2015 04:17, Henry So Jr. a écrit : > The real problem is the lack of a true installation manifest (which a > general problem when installing directly from source) so that you know > exactly what to uninstall when upgrading or uninstalling. That's what > package managers usually do.
Right, that's a good idea. > The problem with removing all instances is a question of what exactly we > need to search for using kpsewhich. gregoriotex.tex? Every file that > might exist under who knows how old a version of Gregorio? All the files that might interfere with the current version of Gregorio, so all files in tex/ I believe. > I also have doubts about the need to run luaotfload-tool every time to > clear the cache. LuaTeX appears to (at least sometimes) be able to pick > up when fonts change, and clearing the cache means that LuaTeX will take > a VERY LONG TIME to run the next time around as it rebuilds the cache. > In other words, this is something to try when things don't work, but > don't do it automatically. That's right. luaotfload should be able to see differences, if you spot cases where it doesn't, please report them (to me or https://github.com/lualatex/luaotfload/), so no need to deal with the cache. > Rather than making this some sort of automatic step under > install-gtex.sh, I propose that we create a "Gregorio cleaner" script > that hunts down old versions and eradicates them using whatever > heuristics we can come up with for finding files, perhaps with some kind > of preview capability. We would also clearly indicate the purpose of > this script in the documentation. We could also then suggest the use of > this script when problems come up. Right, maybe it could be extended with the the ability to create a small gregorio-debug.txt that would contain the results of the different kpsewhich, parse the version of the files, write the vesion of Gregorio, etc. Or maybe a [debug] option in gregoriotex.sty could do that? This would make it easy for windows users who don't have bash... It could be done with a gregoriotex-debug.lua that would be conditionnaly included. The advantage is that it could detect interfereing files in the repository where the compilation takes place. The file could even contain some advices like "you have this file here, please remove it", something like that... What do you think? > After we have this sort of thing in place, we should have a > troubleshooting guide. It might help someone. Absolutely Thank you, -- Elie _______________________________________________ Gregorio-users mailing list [email protected] https://mail.gna.org/listinfo/gregorio-users
