Hi Ezequiel, not going too much into the details (you can search for those), the general approach would be
1) open an account onto a GIT server, github for example 2) create an "organization" for your project (GitHub allows that), so that different types of accounts (developers, administrators, testers, etc) can work on the repositories 3) download locally (repo init + repo sync) AOSP code 4) customize AOSP 5) replace projects in the manifest with your custom projects 6) create a repositories for your customized Android manifest and projects 7) push onto github your custom manifest along with your custom project repos Here's an example: https://github.com/Renesas-EMEV2 (btw - we're looking for voluteering developers for this porting project) Fabio On Friday, 16 November 2012 12:13:04 UTC+1, Ezequiel Aceto wrote: > > Hello, > > I am porting and building Android for a custom hardware, many people will > be working on this version. We would like to have our own repository server > in order to simplify the development of this porting, but I don't know if > this is the best option. > > What it is the best way to archive this? Copying the source to a SVN or > GIT server? With a special REPO command? > > The other question is: once I have this setup done, how to merge changes > from the main Android trunk into my release. > > Thanks very much! > > Ezequiel > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
