On 13 January 2012 00:51, Daniel Espinosa <[email protected]> wrote: > > > Here is what I propose to you: >> >> - remove the generated files from git >> >> >> - add to git the "reference" of these files along with a test script >> (sh, python, perl, ...) which can then compare (or other) the generated >> files with the expected "reference" files to enable you to detect any >> problem. >> >> The advantage of having a script to detect problems is that it can be >> documented (in its header for example) and run by anybody who thinks there >> is a problem. >> >> > for example copy Gda-5.0.gir to libgda/gir ? And then a script to check > diffs?
Yes, for example create a libgda/girtest to store the expected GIR file (managed using git), let the build mechanism create the GIR file in libgda/, and then have a script in libgda/girtest (also managed by git) which compares (or does other tests) the two GIR files after compilation (maybe executed when "make check" is run). Thanks, Vivien
_______________________________________________ gnome-db-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-db-list
