Re: Development primer?
Hi, On 2013-05-11, at 5:28, Christian Stimming (mobil) christ...@cstimming.de wrote: Dear Allen, I'm sorry to hear the program does not start. The error during make check is caused because you don't have the French locale installed. We discussed this here already 3-4 weeks ago. Can someone post the link to that thread here? I'm getting the same error. Thanks, Yawar ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: r23002 - htdocs - htdocs: replace content with a readme file informing everyone the repo has moved to git
On Sunday 26 May 2013 21:32:39 Christian Stimming wrote: Great, thanks! One minor issue: Could you please commit the readme file under trunk, so that updating a trunk working copy will indeed result in the readme file? With the way you've committed right now, updating a trunk working copy will give the error message htdocs-trunk$ svn update svn: Target path '/htdocs/trunk' does not exist which is mildly confusing... Thanks in any case! Christian Hi Christian, That's a valid point. So I have now readded the trunk and branches/beta directories. In each of those I have added the htdocs moved message, with some quick instructions on how to check out the respective branch from git instead. I also point out in there that trunk in svn is now master in git. I tried updating my old svn htdocs checkout of trunk, which gave me no errors anymore. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Guile 2 compatible release tarballs
Let me bring guile 2 up again. The current status is this: - gnucash is ready for guile2, but depends on a very recent version of swig to generate guile 2 compatible wrapper code - in fact *very* recent: swig 2.0.10 has been release today and is the first version of swig capable of generating guile 2 compatible wrapper code Does that mean we *require* swig 2.0.10 ? No. GnuCash 2.5.x works perfectly fine with guile 1.8 and older versions of swig generate code that works fine with guile 1.8. So if you start from our svn/git repository, it's just a matter of personal choice: do I want guile 2 ? Ok, I'll have to make sure I get swig 2.0.10. If that's not an option yet, stick with guile 1.8 and an older version of swig. Working code will be generated in both cases. But what about our tarballs ? There we currently have a problem. The tarballs are shipped with pre-generated wrapper code. So a consumer of our tarballs doesn't have the choice: it has to find a guile version compatible with the pre-generated wrapper code. The currently pre-generated wrapper code is not guile 2 compatible, because it's still generated with an older swig version. This mostly affects distro packagers. Most distros are currently switching to guile 2. Since our tarballs are not guile 2 ready, distros still have to provide guile 1.8 as well. Also it sends the wrong message: we claim gnucash is guile 2 ready, but we ship a tarball that doesn't work with guile 2 ? Not good. So here's my request: can we do future 2.5.x releases on a machine that has swig 2.0.10 installed ? I know it's incredibly recent software, but it would correct the message we send and make the lives of several distro packagers more easy. With future, I don't mean 2.5.2 that's currently in the middle of a release, but perhaps 2.5.3 end of June would be possible ? There is one more devil in the details: while the tarballs for 2.5.x should ideally be generated on a system with swig 2.0.10, tarballs for any possible future 2.4.x releases should *not*. Reason: swig 2.0.10 drops support for guile 1.6, while we claim gnucash 2.4.x does support guile 1.6. So either 2.4.x and 2.5.x releases should be done from different machines or we drop support for guile 1.6 as well in the next 2.4.x release (if any). What do you think ? @John: since you are currently doing most releases, the question is probably aimed mostly at you: are you willing to install swig 2.0.10 on a machine you will be generating tarballs on ? Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Guile 2 compatible release tarballs
On May 27, 2013, at 1:45 PM, Geert Janssens janssens-ge...@telenet.be wrote: Let me bring guile 2 up again. The current status is this: - gnucash is ready for guile2, but depends on a very recent version of swig to generate guile 2 compatible wrapper code - in fact *very* recent: swig 2.0.10 has been release today and is the first version of swig capable of generating guile 2 compatible wrapper code Does that mean we *require* swig 2.0.10 ? No. GnuCash 2.5.x works perfectly fine with guile 1.8 and older versions of swig generate code that works fine with guile 1.8. So if you start from our svn/git repository, it's just a matter of personal choice: do I want guile 2 ? Ok, I'll have to make sure I get swig 2.0.10. If that's not an option yet, stick with guile 1.8 and an older version of swig. Working code will be generated in both cases. But what about our tarballs ? There we currently have a problem. The tarballs are shipped with pre-generated wrapper code. So a consumer of our tarballs doesn't have the choice: it has to find a guile version compatible with the pre-generated wrapper code. The currently pre-generated wrapper code is not guile 2 compatible, because it's still generated with an older swig version. This mostly affects distro packagers. Most distros are currently switching to guile 2. Since our tarballs are not guile 2 ready, distros still have to provide guile 1.8 as well. Also it sends the wrong message: we claim gnucash is guile 2 ready, but we ship a tarball that doesn't work with guile 2 ? Not good. So here's my request: can we do future 2.5.x releases on a machine that has swig 2.0.10 installed ? I know it's incredibly recent software, but it would correct the message we send and make the lives of several distro packagers more easy. With future, I don't mean 2.5.2 that's currently in the middle of a release, but perhaps 2.5.3 end of June would be possible ? There is one more devil in the details: while the tarballs for 2.5.x should ideally be generated on a system with swig 2.0.10, tarballs for any possible future 2.4.x releases should *not*. Reason: swig 2.0.10 drops support for guile 1.6, while we claim gnucash 2.4.x does support guile 1.6. So either 2.4.x and 2.5.x releases should be done from different machines or we drop support for guile 1.6 as well in the next 2.4.x release (if any). What do you think ? @John: since you are currently doing most releases, the question is probably aimed mostly at you: are you willing to install swig 2.0.10 on a machine you will be generating tarballs on ? Yup. No problem. It's just a VM, and it's used exclusively for cross-platform testing and doing Gnucash releases. Building now... Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
[PATCH] Update copyright year and make it translatable
From eb228be6dc15944c24c6818ccd239776f047dcbe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aurimas=20Fi=C5=A1eras?= auri...@members.fsf.org Date: Tue, 28 May 2013 08:51:22 +0300 Subject: Update copyright year and make it translatable --- src/gnome-utils/gnc-main-window.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gnome-utils/gnc-main-window.c b/src/gnome-utils/gnc-main-window.c index ee94405..c83 100644 --- a/src/gnome-utils/gnc-main-window.c +++ b/src/gnome-utils/gnc-main-window.c @@ -4166,7 +4166,7 @@ gnc_main_window_cmd_help_about (GtkAction *action, GncMainWindow *window) { const gchar *fixed_message = _(The GnuCash personal finance manager. The GNU way to manage your money!); -const gchar *copyright = © 1997-2010 Contributors; +const gchar *copyright = _(© 1997-2013 Contributors); gchar **authors, **documenters, *license, *message; GdkPixbuf *logo; -- 1.8.1.2 ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel