Hi all, If you use run-scripts in your Tupfiles, I'd appreciate your feedback. You can reply to the list or reply to me privately if you prefer.
1) What langauge(s) do you use in your run-scripts? Eg: python, shell, etc. 2) What feature(s) do you use run-scripts for that aren't available in the Tupfile parser? 3) Have you tried replacing your run-scripts with the Tupfile.lua files to utilize the Lua parser? If you have but decided to stick with run-scripts, what caused you do to so? For some background: I'm curious how useful they are nowadays. I've tried using python in run-scripts on a large scale project, and found that it didn't work very well. The overhead of a run-script, coupled with the overhead of starting up python for each directory meant that parsing took way longer than it should. As such, I was considering building in python support to improve this workflow. But if we then have regular Tupfiles, Lua Tupfiles, and python Tupfiles, I question the need of a generic script runner. Thanks for your feedback! -Mike -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
