Currently, I do not see a way to make mb write modules to a specific folder. In my case I usually seperate my modules into sites/all/modules/contrib and sites/all/modules/custom. If there is already a way to do this... let me know. If not, I propose the option much like features uses where you can specify a destination folder using the --destination flag.

Comments

generalredneck’s picture

generalredneck
him/his
Primary language English
Location Texas, USA 🇺🇸
CreditAttribution: generalredneck commented

just FYI, I just now started using this tool, and I found out after tinkering with it, it automatically figures out to use /custom. However it might be that in the future i'm actually building a contributed module and would like to add it to contrib instead. What do you think?

joachim’s picture

joachim CreditAttribution: joachim commented

There is an option for where to write the module, just it's called 'parent' rather than 'destination'.

It does however (IIRC) take a full or relative path (though I think I was trying to also get it to take a module name), so I don't know if that makes it at all consistent with Features.

My use case for adding it was creating submodule and test modules, rather than writing to sites/all/contrib, so generally I'd do something like --parent=./tests.