{"action":"created","issue":{"url":"https://api.github.com/repos/gittup/tup/issues/132","labels_url":"https://api.github.com/repos/gittup/tup/issues/132/labels{/name}","comments_url":"https://api.github.com/repos/gittup/tup/issues/132/comments","events_url":"https://api.github.com/repos/gittup/tup/issues/132/events","html_url":"https://github.com/gittup/tup/issues/132","id":17465423,"number":132,"title":"Feature Suggestion: Tupfile.base","user":{"login":"ppannuto","id":339422,"avatar_url":"https://avatars.githubusercontent.com/u/339422?v=3","gravatar_id":"","url":"https://api.github.com/users/ppannuto","html_url":"https://github.com/ppannuto","followers_url":"https://api.github.com/users/ppannuto/followers","following_url":"https://api.github.com/users/ppannuto/following{/other_user}","gists_url":"https://api.github.com/users/ppannuto/gists{/gist_id}","starred_url":"https://api.github.com/users/ppannuto/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ppannuto/subscriptions","organizations_url":"https://api.github.com/users/ppannuto/orgs","repos_url":"https://api.github.com/users/ppannuto/repos","events_url":"https://api.github.com/users/ppannuto/events{/privacy}","received_events_url":"https://api.github.com/users/ppannuto/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2013-07-31T17:37:37Z","updated_at":"2015-12-17T20:47:45Z","closed_at":"2015-12-17T20:47:45Z","body":"I've found it a minor weakness / annoyance of tup that the first time I check out a copy of a repo, I have to remember to run `tup init` before I can `tup upd`. There's a few challenges with running init automatically, the most obvious of which is knowing where the root of the project directory is (assuming it's the current directory feels risky).\r\n\r\nMy proposal is the addition of a new file: `Tupfile.base` (name flexible, maybe `Tupefile.root`, `Tupfile.ini`?)\r\n\r\nThis file would be placed in the root directory of the project to identify it. In addition to identifying the root, I would propose a simple syntax (currently thinking .ini-style syntax) for expressing things such as default variants for the project.\r\n\r\nIn my current mental model, this file is parsed if and only if tup cannot find a .tup directory. More specifically, as `tup upd` begins enumerating directories searching for the .tup directory, it also searches for Tupfile.base (after looking for .tup). If a Tupfile.base is found, the requisite commands are run to initialize things and then tup continues on with `upd`.\r\n\r\nI'm willing to tackle implementing this feature, but I'd like some input on the design first. Is this a good / desirable idea? Do people have comments / suggestions for improving it?"},"comment":{"url":"https://api.github.com/repos/gittup/tup/issues/comments/165577892","html_url":"https://github.com/gittup/tup/issues/132#issuecomment-165577892","issue_url":"https://api.github.com/repos/gittup/tup/issues/132","id":165577892,"user":{"login":"gittup","id":762529,"avatar_url":"https://avatars.githubusercontent.com/u/762529?v=3","gravatar_id":"","url":"https://api.github.com/users/gittup","html_url":"https://github.com/gittup","followers_url":"https://api.github.com/users/gittup/followers","following_url":"https://api.github.com/users/gittup/following{/other_user}","gists_url":"https://api.github.com/users/gittup/gists{/gist_id}","starred_url":"https://api.github.com/users/gittup/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gittup/subscriptions","organizations_url":"https://api.github.com/users/gittup/orgs","repos_url":"https://api.github.com/users/gittup/repos","events_url":"https://api.github.com/users/gittup/events{/privacy}","received_events_url":"https://api.github.com/users/gittup/received_events","type":"User","site_admin":false},"created_at":"2015-12-17T20:47:45Z","updated_at":"2015-12-17T20:47:45Z","body":"I think we can close this, given the #133 has been merged."}}