The problem is caused by leftover files from a previous install.
The solution is to uninstall GnuCash before installing a new version in such cases.
This commit adds a compatibility test and uninstall step to the windows installer
that will automatically uninstall the previous gnucash release if it is considered
'incompatible' with the one to be installed. The user will be warned of this, so
he can decide to cancel the installation if he doesn't like the idea of uninstalling
his working GnuCash installation.
Currently, versions are considered 'incompatible' if their major or minor version
components are different, so 2.3.x is incompatible with 2.2.x and will trigger
an uninstall. Likewise, a 2.4.x install is incompatible with a 2.3.x and will
trigger an uninstall. This is a nice way to remove all testing 'cruft' from the
system once the new release comes out.
Note that in the future installing 2.3.16+ over 2.4.x will also trigger the uninstall, which is
a good thing IMO. An older release can't know about changes made in a newer one,
so it's safer to first uninstall the newer one to avoid leftover files.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19528 57a11ea4-9604-0410-9ed3-97b8803252fd
* reduce footprint by not packaging unused files
* move gnc-mod required files to bin
* remove libdir from the PATH
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19513 57a11ea4-9604-0410-9ed3-97b8803252fd
He wrote to gnucash-devel on 2010-08-28:
Much of the last batch code I contributed to gnucash was licensed
without the "or any later version" clause of the GPL boilerplate, and
thus specifically and only under version 2 of the GPL.
I hereby extend that to version 2 and/or version 3.
Any contribution I've made to gnucash which was under the GPLv2 only may
be considered to be under both v2 and v3.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19507 57a11ea4-9604-0410-9ed3-97b8803252fd
This should have never appeared in a user message. However, in order
not to make this single string untranslated, we add the correct form
but don't use it yet so that it can be translated, and we will be
using it once 2.4.0 is out and the string freeze lifted.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19506 57a11ea4-9604-0410-9ed3-97b8803252fd
This is a step to make gnucash more run-time relocatable.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19505 57a11ea4-9604-0410-9ed3-97b8803252fd
when multiple installations of GnuCash exist (like stable and devel version on one system).
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19504 57a11ea4-9604-0410-9ed3-97b8803252fd
The values set on the command line were never used.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19499 57a11ea4-9604-0410-9ed3-97b8803252fd
One is on the price editor. Namespace: is not marked translatable.
Another is about a tip for account editor window. The label
"Edit->Income tax Options" was
changed to "Edit->Tax Report Options" but an old msgid remains on tip.
The last is on the Tax Table. The label "_Edit" is not marked
translatable but it should be.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19474 57a11ea4-9604-0410-9ed3-97b8803252fd
The implementation is a hacky workaround, but at least better than
having weird translations as in the current state. Note: Even
though new strings are introduced, they are not yet used in order
not to break the string freeze here. The new strings need to
be activated once the 2.4.0 string freeze is lifted.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19469 57a11ea4-9604-0410-9ed3-97b8803252fd
We need to locally store a reference to that particular GWEN_GUI
object that was used in Extend because we have more than one such
object in use inside gnucash (currently). If accidentally the wrong
one would be used in Unextend, a crash occurs.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19465 57a11ea4-9604-0410-9ed3-97b8803252fd
Fix minor memory leak in gnc_sx_get_current_instances(void) - was not
free'ing the GDate of now.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19459 57a11ea4-9604-0410-9ed3-97b8803252fd
Also, replace "void *" by pointers to the actual type.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19458 57a11ea4-9604-0410-9ed3-97b8803252fd
This will ensure that users won't lose the settings they stored in saved reports
and open report windows when switching from 2.2.x to 2.4.
Note that this only works in one direction, from 2.2.x to 2.4. If a user switches
back to 2.2.x, the open report windows will lose many settings, almost resetting
them to their default state. Saved reports won't have this problem as they are
copied to a new file during the migration.
In detail:
For open reports:
pre-2.3.15 -> 2.3.15+ : options for open reports will be migrated
2.3.15+ -> pre-2.3.15 : options for open reports will be migrated
For saved reports:
2.2.x -> 2.3.15+ : all options will be migrated, if saved-reports-2.4
does not yet exist
pre-2.3.15 -> 2.3.15+ : options for saved reports won't be migrated but reports
continue to work. It would be best to save the reports again,
but my scheme-fu is not good enough to let the code do that
automatically. Alternatively users should remove the file
saved-reports-2.4 to recreate it on the next run, based on
saved-reports-2.0.
2.3.15+ -> 2.2.x : options are unaffected, sine 2.2.x and 2.15 use different
saved reports files
2.3.15+ -> pre-2.3.15 : reports saved in 2.3.15 will lose their options, older reports
are unaffected. But returning to 2.3.15+, the options will
continue to work.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@19451 57a11ea4-9604-0410-9ed3-97b8803252fd
