Op vrijdag 26 april 2019 16:44:03 CEST schreef John Ralls: > > I am aware I suggested on irc to put the tarball on sourceforge. However > > while seeing this commit I wonder if there's a reason not to do as we did > > for guile 2.0: start from the upstream tarball and apply patches during > > the build ? That would mean storing the patches in our gnucash-on-windows > > repo. > The last Guile release was almost a year ago and I'm not able to get it to > build, so the patch set to that tarball would have to incorporate all of > the commits to bring it current with stable-2.2. If the Guile team would do > a release then we could reasonably use that tarball. In an ideal world it > would include my patches [1][2] and we could use it unmodified. > Oh, in that case, let's just stick with our own guile tarball until the guile team does another release. Perhaps make a note of this somewhere so we remember in a year or so why we did this.
Geert > Regards, > John Ralls > > [1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35405 > [2] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35430 _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
