Re: [fossil-users] Nested check-outs
Hi Will, fossil open --nested allows opening a fossil within an existing checkout. This question came up earlier this week as well; it may be worth looking at the archives. Solutions included fossil open --nested and scripting a checkout of external dependencies. Cheers, Gareth On Thu, 17 Nov 2011 04:38:49 -, Will Duquette w...@wjduquette.com wrote: Howdy! Is there a document that describes the best practices for a project that involves components from multiple fossil repositories? For example, suppose I've got an infrastructure library that is in its own fossil repository. And I've got an application that uses that infrastructure library. With Subversion, I'd do an svn:external to pull the infrastructure library into my working area as a subdirectory. Is there an equivalent way to do this with fossil that won't get me into trouble? Thanks very much! Will Mr. Will Duquette, OP will -at- wjduquette dot com http://foothills.wjduquette.com/blog ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Nested check-outs
On Nov 17, 2011, at 2:04 AM, Gareth Roberts wrote: Hi Will, fossil open --nested allows opening a fossil within an existing checkout. This question came up earlier this week as well; it may be worth looking at the archives. Solutions included fossil open --nested and scripting a checkout of external dependencies. Thanks, Gareth. I knew I'd seen something, but I couldn't remember enough about what it was to even go looking for it. If I understand it correctly from the previous posts to the list, using fossil open --nested just allows a nested checkout to live within a parent checkout without confusing fossil; but the two checkouts are essentially separate. In other words, it's like a Subversion svn:external, except that fossil doesn't check it out for you automatically; you have to do that yourself (i.e., by make getmydependencies or something like that). Thanks! Cheers, Gareth On Thu, 17 Nov 2011 04:38:49 -, Will Duquette w...@wjduquette.com wrote: Howdy! Is there a document that describes the best practices for a project that involves components from multiple fossil repositories? For example, suppose I've got an infrastructure library that is in its own fossil repository. And I've got an application that uses that infrastructure library. With Subversion, I'd do an svn:external to pull the infrastructure library into my working area as a subdirectory. Is there an equivalent way to do this with fossil that won't get me into trouble? Thanks very much! Will Mr. Will Duquette, OP will -at- wjduquette dot com http://foothills.wjduquette.com/blog ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Mr. Will Duquette, OP will -at- wjduquette dot com http://foothills.wjduquette.com/blog ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Nested check-outs
Howdy! Is there a document that describes the best practices for a project that involves components from multiple fossil repositories? For example, suppose I've got an infrastructure library that is in its own fossil repository. And I've got an application that uses that infrastructure library. With Subversion, I'd do an svn:external to pull the infrastructure library into my working area as a subdirectory. Is there an equivalent way to do this with fossil that won't get me into trouble? Thanks very much! Will Mr. Will Duquette, OP will -at- wjduquette dot com http://foothills.wjduquette.com/blog ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users