Essentially the request here is to support a relative path to the .fossil file in the _FOSSIL_ file. This would be very useful for me and as far as I can tell there is no good technical reason why it would not work just fine.
John's desired work strategy can easily be supported with the relative path suggestion. For me has has been *really* annoying to have mounted a disk with a fossil dir such that the relative location to the .fossil is unchanged but the absolute location is different and not be able to run "fossil status" to check that everything was committed. Another example were this was really annoying is where I mounted a directory in a virtualbox instance and again, no fossil operations are possible. A third example ; to keep things simple for new users I wrote a wrapper script that makes getting a repo a single command. The wrapper puts the .fossil file inside a directory .fossil in the repo. Now if the user decides to move the fossil area then fossil commands will no longer work. All of these can be "worked around" but it sure seems lame. I see two possible strategies on how to implement this: i. Use the path to the .fossil as given on clone command line as-is. ii. If the path to the .fossil lies inside the clone area then use a relative path. Either approach would work for me. The second seems more conservative but may be more work to implement. Just my $0.02 On Sat, Jan 28, 2012 at 1:26 PM, Stephan Beal <sgb...@googlemail.com> wrote: > On Sat, Jan 28, 2012 at 9:23 PM, John Found <johnfo...@evrocom.net> wrote: > >> Unfortunately the suggested workaround is not very useful, because I need >> only one >> check out, because the changes I make in Linux, later must be tested in >> Windows and >> vice versa. At the end, when everything works I can make commit with all >> changes. >> > > How does having two checkouts prohibit you testing from both platforms? > You develop on windows, check in the changes, switch to linux, update that > checkout and test the changes there. > > _FOSSIL_ _has_ to record where the original .fossil file is (because in > 99% of cases it is NOT the current directory, and even if it was always in > the current dir, it wouldn't know the file's name). The approach of trying > to recycle a single checkout for two platforms is the source of your grief, > and the workaround is to stop doing it. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
