On Thu, Sep 7, 2017 at 5:41 PM, Kevin Quick <[email protected]> wrote: > 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?
Hi Kevin, I believe processing Tupfile.ini as an options file was part of the original intent in https://github.com/gittup/tup/issues/132, though during the actual pull request in https://github.com/gittup/tup/pull/133 that functionality was removed at my request. My rationale at the time was that the majority of the options that you can set are user preferences, and wouldn't make sense to commit to a repo (see: https://github.com/gittup/tup/pull/133#issuecomment-23383066). Are there specific options that you think would be useful to process at the project level instead of the user level? Somewhat related, see https://github.com/gittup/tup/issues/266 for a good idea of unifying the option filenames, though that would be a backward-incompatible change. -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.
