On Oct 21, 2012, Richard Hipp <[email protected]> wrote: > > > >On Sun, Oct 21, 2012 at 3:19 AM, K <[email protected]> wrote: > > > >Hello, > > > >I have a project which is currently comprised of three components; one library >and >two programs which include the library. > > > >What would be, if any, the benefits to using a single repository for these 3 >products >vs 3 individual repositories? > >The SQLite project (for which Fossil was designed) is kept in multiple >repositories. >There is one repository for the main SQLite source code and the TCL test >suite. >There is a separate repository for the documentation. Two other repositories >host >the TH3 and SqlLogicTest test suites. Then there are separate repositories >for proprietary >extensions, SEE, CEROD, and ZIPVFS. > > > >I don't know that this necessarily the best way to organize things. But it >has worked >well for us so far.
Ok, so fairly modular. Given several repositories for a single project, what is the preferred manner of 'linking' these repositories for purposes such as consolidated user auth/credentials? > > > > > > > > >^K > >_______________________________________________ > >fossil-users mailing list > >[email protected] > >http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > >-- >D. Richard Hipp >[email protected] > > > >_______________________________________________ >fossil-users mailing list >[email protected] >http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
