I personally would prefer 2, because buncing everything into one role would be too inflexible. I don't see much maintenance overhead if compared with 1.

On Fri, Jul 18, 2014 at 6:19 PM, Juliusz Gonera <jgonera@wikimedia.org> wrote:

I talked to Dan Duvall today and he said that many mobile browser
tests fail on default vagrant instance because other extensions that
are not hard dependencies of MF are not activated by default when
activating the mobilefrontend role (extensions such as Echo, GeoData,
VisualEditor). There are two things we can do:

1. Make other extensions that mobile uses dependencies of
mobilefrontend role in vagrant
2. Create a separate role, e.g. mobilefrontend-browsertests, that will
list mobilefrontend and all those extensions as its dependencies

I was wondering if there is anyone who uses vagrant and would like to
have MF enabled, but not all the other extensions. If not, 1. seems
like a simpler solution.

Thoughts?

--
Juliusz