Page Comparison

In-Portal repository has following structure:

???|-- 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

...

1. remove the profiles concept from repository
2. create the "configure_profile.shphp" file within "tools" folder that accepts single argument "profile name"

...

1. checkout main in-portal folder from svn://source.in-portal.org/in-portal/branches/5.2.xinstead  instead of checking out profile-name from svn://source.in-portal.org/profiles/profile-name/branches/5.2.x we 
2. run "php /tools/configure_profile.sh php profile-name", which will set needed "svn:externals" property
3. run "svn update" once to checkout modules/themes that were added

The same script, that currently handles "svn:externals" property generation for profiles needs to be updated to generate the "configure_profile.shphp" 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.

Related Tasks