Yes, the Source tab instructions are customizable. I'm not sure what you mean by 'reference the code'... you can just leave all the projects living in their separate svn repositories as is, or you can re-import them into a new 'super' repository. The choice is yours:
* if you just want to point to them, go for it. You can use the svn:externals feature such that by checking out the 'main' repository, you automatically get checkouts of the individual repositories too. (Maybe this is what you meant?) svn:externals is described in the svnbook. * if you want to merge the code into one big repository, you can do the easy thing -- just 'svn import' the latest code from each project into its own top-level directory -- or you can do the harder history-preserving thing -- 'svnsync' each repository to local disk, 'svnadmin dump' each history, 'svnadmin load' each history into a new master local repository, then 'svnsync' the merged repsoitory back to google code. (Revnums will all change, of course, but each project's history will still be present in the merged repository.) On Wed, Oct 20, 2010 at 10:47 AM, Rui <[email protected]> wrote: > Dear Ben, > > Thank you for the quick reply. > > In terms of the version control, what about the projects are already > hosted on Google Code? Is there a way to reference the code at the SVN > level? > > Also, is it possible to modify the source tab to provide download > options for different projects? > > Many thanks, > Rui > > On Oct 20, 3:51 pm, Ben Collins-Sussman <[email protected]> wrote: >> From the version control point of view, it's perfectly normal to put >> all the projects into a single Subversion repository: give each >> project a top-level directory, with standard {trunk, branches, tags} >> directories underneath each one. >> >> Or, if you want to use Mercurial, you can create a number of >> independent "top level" repositories -- one for each project. >> >> The issue tracker may be trickier. If all the projects share one, you >> may want to use the flexible labeling system, and be sure to create >> some sort of set of "component" labels to clearly identify which >> subproject the bug is referring to. >> >> On Wed, Oct 20, 2010 at 8:02 AM, Rui <[email protected]> wrote: >> > Hi All, >> >> > We have a bunch of related small projects which we would like to host >> > on Google Code, some of them are already on Google Code, some of them >> > have not been uploaded yet. In short, these projects can be used >> > either together or independently. To increase the visibility of these >> > projects, we are just thinking of creating a parent project which >> > provides a single entry point to all of these small projects. >> >> > We are just wondering whether it is possible to do this? And do you >> > have any recommendations on how to go about this? Also, what would you >> > do in terms of managing the source code? One super repository for all >> > the projects vs one repository for each project? >> >> > Many thanks, >> > Rui >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Project Hosting on Google Code" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group >> > athttp://groups.google.com/group/google-code-hosting?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
