On 3/13/2017 8:57 AM, Richard Hipp wrote:
On 3/13/17, Stefan Bellon <sbel...@sbellon.de> wrote:
When upgrading from 1.24 to 1.29 years ago, the output of "fossil
annotate" changed and broke all our scripts (and even some customer
databases).
I expect even more incompatibilities when switching from 1.29 to 2.0
and therefore this is nothing that can be done in a few minutes.
We have to check for all the output of all fossil commands we use in
scripts whether they still produce the same output they did before.
I'm a little confused. If you need to continue using Fossil 1.29 for
text output compatibility, then why is it a problem that you cannot
"fossil update" to the latest trunk? After all, you won't be using
the latest trunk, right?
Also: 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? What are your scripts doing? 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?
When fossil is configured to include JSON support it has a fossil json
command that consumes a JSON object full of command and arguments and
returns a JSON object of results. A similar feature is available over
HTTP(S) through URLs beginning with /json.
Unfortunately JSON support is not configured in the default builds of
fossil. I often turn it on for my personal builds, because I have some
scripts that draw from the ticket system for report writing, and the
JSON support for reading and querying tickets works quite nicely. I'd
personally like to see the JSON support trusted enough to be on by default.
Also, not every command is available via JSON, and I suspect that there
is no JSON equivalent to fossil annotate. If we can figure out how to
represent the annotate/blame/praise data in JSON, then adding it should
be possible.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
