[ClusterLabs Developers] [pacemaker] downstream packagers&direct consumers: is bison prereq OK with you?

[Jan Pokorný]

It seems extraneous to carry results of *.y files processing the
tree (and hence in what we call distribution tarballs at the time).
Hence the simple question, are you OK with bison (not yacc, even
though the compatibility fix appears to be a sed oneliner) becoming
a new dependency?

It's also not clear, provided that's fine with you, whether there
should still be some wiggle space, making the feature that would
require that optional, even though I'd prefer the strict uniformity
here for documentation purposes etc. (unless the platform at hand
is not catching up, something like < 3% of deployments, perhaps).

At this point very tentative context for the curious
(currently carries both *.y and respective *.c, but I don't like
the diffstats at all :-)

  https://github.com/ClusterLabs/pacemaker/pull/1756

Please, speak up.

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/developers/attachments/20190426/258fd122/attachment.sig>