I'm looking at possibly using gitorious inside a corporate environment, and am finding it difficult to figure out how use the project/repository hierarchy to reflect what we really do/need.
Suppose we map the gitorious "project" concept to the notion of a "product". The product consists of multiple subsystems, and we map a subsystem to a gitorious "repository". Now, suppose that we define another product, so we create a new "project". Some of that product's subsystems will be unique to the product, but, if we do a good job at re-use, some of the subsystems from the first product can also be re-used. How do I use the same repository in both project A and project B? Now, if I can't share repositories across projects, what are my alternatives? Do I need to "promote" a shared repository out of project A into its own project? If that's the case, how do I set up the dependencies between project A and project SharedComponent and, similarly, between project B and project SharedComponent? Finally, I've yet to find any kind of document/wiki/blog/etc. that discusses this aspect of gitorious. Have I missed it? I am happy to RTFM if someone can point me towards TFM. Thanks! -cj -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "Gitorious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
