On Wednesday 02 of December 2015 17:30:42 Freddie Chopin wrote: > I'm going to update tup in a moment and > test it with ".config" files.
As could be expected, the new version of tup works flawlessly when I configured my project to use ".config" file as an input for tup (parsed by lua and treated like a sort-of config.tup) and as an input for commands. For now I did not notice any problem and I actually don't expect any (; You might want to ignore other hidden folders of popular version control systems - ".svn" would be a good candidate. As for the configuration of such folders - maybe default set could be listed in /etc/tup/options (C:\ProgramData\tup\tup.ini on Windows) file, and the user could override that with his/her own .ini files (preferably Tupfile.ini in root of the project) to whatever is needed (if different than default)? The only folder that must be always ignored is ".tup" - so it would be compiled in the executable and ignored no matter what the user does - everything else could be an option in that case. Regards, FCh -- -- 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.
