On Tue, Jul 17, 2018 at 7:57 PM Nikita Popov <nikita....@gmail.com> wrote:

>
> Ah yes, *of course* the generated files will be part of distribution
> tarballs, just like we do with all generated files (not just the parser,
> but also configure.) While I forgot to write this in my original mail, it
> has been mentioned already 4 days ago. So again, it seems like we're really
> in total agreement here, just a matter of turning it into reality ;)
>

You know, you made me go back to Sara's email where she disagreed with me,
only to find she actually was disagreeing with Remi's proposal to track the
generated files for releases in git.  That's definitely not a hill to die
on for me :)

So all in all I think you're right, we agree on the important things:
1. Remove generated files from git
2. Keep them in source packages

What we seem to disagree on is that we should have a narrower list of
acceptable re2c versions determined by configure/makedist.  This isn't a
hill to die on for me either, although I think that narrowing it down is
better in terms of our ability to deliver a source package with confidence,
and be sure that everyone who's testing/using it is testing the same thing
(similar to how we do it with bison).  Arguably it's more important to be
on the safe wide with makedist than it is with configure.

Thanks,

Zeev

Reply via email to