gaspaio/Drupal-Profiles — comment on commit def0698af077be3a4c8645af87e6369b4d0fbb44
File:  line 0
By patcon:

so basically, your stub can be like this:

```
core = 7.x
api = 2

projects[pressflow][type] = core
projects[pressflow][download][type] = git
projects[pressflow][download][url] = https://github.com/pressflow/7.git
projects[pressflow][download][revision] = 86e637864707e

projects[mydev][type] = profile
projects[mydev][download][type] = git
projects[mydev][download][url] = file:///path/to/mydev/.git
```

Downsides:
* Can't accept relative paths (so isn't universal)
* when you're working on a deployed site, can't natively do an edit-then-push in $DRUPAL_ROOT/profiles/mydev/ until you run `git remote set-url origin git@example.com:mydev.git` or whatever.
* Need to remember to go back and commit the newest submodule ref in mydev-build.git whenever you update the mydev.git profile itself.

Advantages:
* Can test changes to install profile without commiting, which keeps untested junk outta logs.
* Can't always keep the buildfile with the remote url in VCS, then create a quick copy for local testing, easy-peasy
* allow for an easy place to put tests and other files that easily stays in lockstep with profile, and if you're adding acceptance tests related to added functionality, this is helpful
* For cont. integration, you can granularly commit to profile itself, but just have ci server look for changes in mydev-build repo, so only when you update submodule will it launch the automated testing suite (presumeably when you're adding tests too)

Advantages. Can build