In-Portal repository has following structure:
| No Format |
|---|
???|-- in-portal ?| ???|-- branches ?| ???|-- releases ?| ???|-- trunk ???|-- modules ?| ???|-- module-name1 ?| ?| ???|-- branches ?| ?| ???|-- releases ?| ?| ???|-- trunk ?| ???|-- ... ???|-- profiles ?| ???|-- profile-name1 ?| ?| ???|-- branches ?| ?| ???|-- releases ?| ?| ???|-- trunk ?| ???|-- ... ???|-- themes ?| ???|-- theme-name1 ?| ?| ???|-- branches ?| ?| ???|-- releases ?| ?| ???|-- trunk ?| ???|-- ... |
So there is:
- single "in-portal" folder
- a folder per module
- a folder per profile
- a folder per theme
...
The same script, that currently handles "svn:externals" property generation for profiles needs to be updated to generate the "configure_profile.sh" file.
More benefits
Since now we checkout main in-portal repository, then it becomes possible to use Phabricator's tool called Arcanist: https://secure.phabricator.com/book/phabricator/article/arcanist/ which is basically a CLI tool for http://qa.in-portal.org/ website to simplify code contribution.