[gtkada] Patch: Add a command variable for Python.

Emmanuel Briot briot at adacore.com
Mon Feb 3 09:25:41 CET 2014


> And also simplifying the work of other packagers in other distributions,
> as well as users who choose to build locally. That's an important part
> of why I submit patches.

Sure, although it's always hard to know who needed them or not. For instance,
Ludovic Brenta apparently did not have the same requirements when he did
the packages for Debian. 

> OK, and what do you do if you're not satisfied with one of the Ada
> files? I assume that you will either improve binding.py until it

Sure, or add exceptions in binding.xml.
The point is that unless you are using the exact same setup, we can't be
sure you are generating the same sources.

> As for the specific Python version, Fedora does have Python 2.7 as the
> default version (and my patch was intended to facilitate selecting
> Python 2.7 in environments where it's available but not the default).

The patch has been included, by the way, although that doesn't change
the usefulness of this discussion.

> Perhaps I'll move the pre-generated files to the side, run "make
> generate", delete tmp.ada, and compare the generated files to the
> pre-generated ones. If they turn out to be different the build will
> fail and I'll have to investigate. That way I should get as close as I
> can to the goal of ensuring that all generated code can be regenerated,
> while also ensuring that the code being compiled is the same as what
> you have reviewed and tested.


Sounds like a plan indeed, so that you can check whether you are able
to generate those files (still not sure what added quality insurance that
gives you, but certainly fine for the final users).

regards
Emmanuel


More information about the gtkada mailing list