On Wed, 14 Dec 2016, mostolog--- via rsyslog wrote:
To solve this hopefully once and forever, I googled again for "sphinx
dot" and the first result seems to be fully appropriate:
http://www.sphinx-doc.org/en/1.4.8/ext/graphviz.html
As I said two weeks or so ago, we need to check if we have
sufficiently current sphinx on the involved systems, but the first
step is to read and use what is describe, to see if it actually fits
the need.
Yes, but my point is that doesn't properly render on github. I'll love to
have documentation (with graphs) on github, but I'll have to stick to
sphinx+rsyslog.com if that doesn't work. That's why I tried gravizzo (or
whatever the name is)
I know I've seen discussions on these sorts of things in the past on other
lists.
What we need here is makefile magic where a file can be in the repository, but
also optionally generated by a build. If the file is up-to-date compared to it's
source (later timestamp), the makefile doesn't try to build it, and therefor
doesn't require the dependency of the tools needed for the build, but if the
generated file is older than it's source, the make will look for the tools it
requires to build the file (complaining if they aren't there), and then
re-generate it.
If someone can do the research on how to best do this, we could also use it for
the bison/yacc dependency.
This is good for generated files that don't change much, which both the diagrams
and the grammer match
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
