On Fri, Nov 7, 2014 at 2:42 AM, Tony Papadimitriou <to...@acm.org> wrote:
> There is also another possibility. Under Windows, you can use the MKLINK > command to create a directory junction under your project (each project). > This way you can keep the tree structure you have, keep a single copy of > your libraries, but make it appear as if each project has its own copy. > FOSSIL will treat this as a normal directory, meaning that if you open the > repo somewhere else (where the junction does not exist), you will get a > copy of you library. > > One potential problem with this approach is that, even though there is a > single copy of the library, each project thinks it has a private copy. So, > making library changes for the sake of one project have to be propagates to > all other repos using the same library in their projects. Fossil supports nested checkouts. Maybe if the link/directory junction pointed to a checkout of the shared library, Fossil will behave as though the library checkout was an actual nested checkout.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
