Geert Janssens <janssens-ge...@telenet.be> writes: [snip] > What do you think ? Which solution would be preferable and realistic > (in terms of effort vs gain) ?
I think it would be cool if there were some way in the 'branch' to say what build system is required. Then we could effectively do: - checkout branch/tag - run "the buildsys requires script from the checkout" - build the checkout Perhaps we would need to have a local mapping of buildsys names to local paths, but this would make it future-proof. If we require additional build environments we just install them side-by-side, create a global name and extend the local map, and then we just declare which buildsys we need to use. > Geert > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=621238 > [2] https://bugzilla.gnome.org/show_bug.cgi?id=615168 Keep in mind that tag build always rebuild all dependencies from scratch, so this approach would work. Similarly, if we were going to set up a daily or weekly "branch build" then we would need a separate checkout and could certainly have a separate set of dependencies there, too. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warl...@mit.edu PGP key available _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
