On Tue, 28 Mar 2017 09:16:33 +0200, Florian Balmer
<florian.bal...@gmail.com> wrote:
Citation from:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg24841.html
... What can we do to help you move away from scripts that depend
on the details of command-line output and toward something that is
more likely to survive an update? ... Would it be better to run
SQL queries directly against the repository database? ... Are new
fixed-output-format commands needed in Fossil to extract
information that is important to scripts?
I'm working with a lot of scripts to process Fossil command-line output.
The JSON interface is not available with some of the precompiled
binaries I'm using, and parsing JSON from shell scripts or Windows
batch files seems not so trivial.
Running SQL queries directly would mean to reinvent the wheel and
perform complex operations in many cases, as i.e. the output of
`fossil whatis [check-in]` involves parsing and integrating all
amendments to a check-in (or thorough knowledge of the internal Fossil
storage format if this information is cached in some table).
Therefore, I would like to vote for the command-line output to remain
as stable as possible, make the suggested "fixed-output-format" the
default, and carefully document modifications to the command-line
output format in the Fossil change logs.
+1
--Florian
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
