{"action":"created","issue":{"url":"https://api.github.com/repos/colinmollenhour/modman/issues/95","labels_url":"https://api.github.com/repos/colinmollenhour/modman/issues/95/labels{/name}","comments_url":"https://api.github.com/repos/colinmollenhour/modman/issues/95/comments","events_url":"https://api.github.com/repos/colinmollenhour/modman/issues/95/events","html_url":"https://github.com/colinmollenhour/modman/issues/95","id":79036902,"number":95,"title":"Feature request: common path prefix","user":{"login":"nevvermind","id":834932,"avatar_url":"https://avatars.githubusercontent.com/u/834932?v=3","gravatar_id":"","url":"https://api.github.com/users/nevvermind","html_url":"https://github.com/nevvermind","followers_url":"https://api.github.com/users/nevvermind/followers","following_url":"https://api.github.com/users/nevvermind/following{/other_user}","gists_url":"https://api.github.com/users/nevvermind/gists{/gist_id}","starred_url":"https://api.github.com/users/nevvermind/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nevvermind/subscriptions","organizations_url":"https://api.github.com/users/nevvermind/orgs","repos_url":"https://api.github.com/users/nevvermind/repos","events_url":"https://api.github.com/users/nevvermind/events{/privacy}","received_events_url":"https://api.github.com/users/nevvermind/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-21T15:07:50Z","updated_at":"2015-05-21T17:01:50Z","closed_at":null,"body":"When creating modules, we usually put all its files under `src`, because we may have some tests, unrelated files in the repo etc. and we want to keep them separated. But we want to `modman` file at the repo's top level as well.\r\nSo we end up mirroring the folder structure except the `src` part, which we always have to append.\r\n\r\nWould it be difficult (and I mean BC breaks here) to add a common source folder _once_ and the bash script prepends it on every subsequent source path? For exampled, instead of\r\n```\r\nsrc/app/code/community/MX/*          app/code/community/MX/\r\nsrc/app/etc/modules/MX_Module1.xml   app/etc/modules/\r\n```\r\n... we could use this type of declaration (without mentioning the target path):\r\n```\r\n#[source=\"src/\"]\r\napp/code/community/MX/\r\napp/etc/modules/\r\n```\r\nLike a dynamic CHDIR.\r\n\r\nPS: The coment-syntax is completely bogus. No idea what syntactic constraints are there."},"comment":{"url":"https://api.github.com/repos/colinmollenhour/modman/issues/comments/104355458","html_url":"https://github.com/colinmollenhour/modman/issues/95#issuecomment-104355458","issue_url":"https://api.github.com/repos/colinmollenhour/modman/issues/95","id":104355458,"user":{"login":"riconeitzel","id":930706,"avatar_url":"https://avatars.githubusercontent.com/u/930706?v=3","gravatar_id":"","url":"https://api.github.com/users/riconeitzel","html_url":"https://github.com/riconeitzel","followers_url":"https://api.github.com/users/riconeitzel/followers","following_url":"https://api.github.com/users/riconeitzel/following{/other_user}","gists_url":"https://api.github.com/users/riconeitzel/gists{/gist_id}","starred_url":"https://api.github.com/users/riconeitzel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/riconeitzel/subscriptions","organizations_url":"https://api.github.com/users/riconeitzel/orgs","repos_url":"https://api.github.com/users/riconeitzel/repos","events_url":"https://api.github.com/users/riconeitzel/events{/privacy}","received_events_url":"https://api.github.com/users/riconeitzel/received_events","type":"User","site_admin":false},"created_at":"2015-05-21T17:01:50Z","updated_at":"2015-05-21T17:01:50Z","body":"What about a system variable setting this and modman checks for that? That would mean it's system wide but at least it's something \n\n> On 21 May 2015, at 18:30, Colin Mollenhour <notifications@github.com> wrote:\n> \n> Makes sense, but currently modman syntax is more or less working with composer and this new feature would break the compatibility with composer.. Not a huge issue really but it would add confusion for some people when they are using an old version and their modman files suddenly don't work. Also more documentation needed to explain the feature, etc.. So I personally would rather keep it simple/compatible and have slightly more verbose modman files. Would like to hear more people's opinions though.\n> \n> One alternative (also not composer compatible but at least is already supported) is to have the root modman file like this:\n> \n> @import src/\n> And then another modman file inside of src/:\n> \n> app/code/community/MX/\n> app/etc/modules/\n> —\n> Reply to this email directly or view it on GitHub.\n> \n"}}