On 5/10/2017 7:08 AM, David Mason wrote:
I generate the initial fossil for them. The problem is that I don't
control, e.g. executable names, so if they have foo.c and say `make
foo` they will have foo.o which I can match, but also foo which I
can't (because they might call it foox.c - and hence foox - instead).
Because I generate the initial fossil the `:::BINARY:::` pattern in
the ignore-glob file is viable, as would be a `:::SizeOver:::100000`
pattern.
Here is an example of where Windows is slightly better off. By clearly
designating a binary executable as `.exe`, you can put that in the
ignore-glob and be confident.
Unfortunately, file globs are not regexps so you can't ignore any file
without a dot in its name. But you could if we included a feature that
Git has, allowing ! at the front of a glob to invert the match. If we
had that (and comment lines in glob files), I think this might work:
# ignore obvious build targets
*.o *.d *.a *.so
# ignore files without at least one dot somewhere in their name
!*.*
# and for Windows
*.obj *.lib *.dll *.exe
But that will treat "lesson.one/foo" as allowed, not ignored as you
might have preferred.
Having a way to use SQLite's REGEX instead of GLOB for filename matching
on a case-by-case basis would also be a solution. It would allow writing
a regex that excludes "lesson.one/foo", at least. Not sure what the best
notation to propose for that would be, or if the REGEX operator is
enabled in fossil's loaded SQLite.
--
Ross Berteig [email protected]
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
