I would like to be able to specify project-specific tup options that I can 
commit in my VCS, but only .tup/options is currently processed, and the 
.tup directory is added to the ignore list for my VCS.

Placing options in the Tupfile.ini at the top level seems like a reasonable 
alternative, and this file is more easily tracked as a versioned file. 
 This can be enabled by a one-line change to add `{ .file = "Tupfile.ini" 
}` in the `locations` list in src/tup/option.c.  Does this change (+ 
documentation) sound reasonable, or are there arguments against this change 
and/or a better way to achieve my goal?

Thanks,
  Kevin

-- 
-- 
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.

Reply via email to