OK; Outstanding, this works like a charm. On Windows 7 Pro (64 bit) the GnuCash installation created:
C:\Users\$USER\.gnucash There is also: C:\Users\$USER\.AppData\Local... \LocalLow ...\Roaming When I copy the files from the linux installation at: $user/.gnucash to C:\Users\$USER\.gnucash, it does indeed find the Saved Report Configurations. My assumption is that Windows 8 and 10 probably will set up the .gnucash config directory in: C:\Users\$USER\.AppData\Roaming, or Local, because 8 and 10 seem to behave that way (I don't know why). I can confirm that the flatpak migrates: $user/.gnucash to: ~/.var/app/org.gnucash.GnuCash It does the migration when installing the flatpak by: flatpak-install or.gnucash.GnuGash (or, depending on the type of shell, just flatpak-install gnucash) The flatpak has some distinct advantages. One drawback is that libraries are not dynamic, static or even linked, but appear to be "bundled" into the installed app binary itself. But that's also the advantage, when linked libraries on linux machines are not found, or are incompatible. Larger installed binary, fewer dependency problems. FreeBSD and linux have cross-compilers for each other, so I might try the flatpak again when I have FreeBSD 10 or Ubuntu 18 installed. Again, the flatpak looks and works fine. Only the window configuration (so far) is the problem with the flatpak. Is there an advantage to using GnuCash 3 on Windows 8 or 10? Windows 7 is showing it's age, and it's taking some time to load reports, open files, etc. Mange Tak, Gordon On Tue, Sep 17, 2019 at 3:33 AM Geert Janssens <geert.gnuc...@kobaltwit.be> wrote: > > Op maandag 16 september 2019 05:30:16 CEST schreef John Ralls: > > Gordon, > > > > GnuCash files are completely portable between operating systems. See > > https://wiki.gnucash.org/wiki/Backup for the details of which files need to > > be copied. > > > > The code to upgrade the saved reports and similar stuff kicks is driven by > > the location of the files, so copy your 2.6 config files to the 2.6 > > locations (generally $HOME/.gnucash). Make sure the new locations > > ($HOME/.config/gnucash on Linux, $HOME/AppData/Roaming/GnuCash on Windows) > > don't exist; if they do GnuCash will decide that the config is already > > migrated. Start up GnuCash and everything should properly migrate. > > > > That said, flatpak installs are a bit problematic for migration. They're > > seriously sandboxed and I'm not sure that we've figured out everything > > needed to work around the sandboxing. > > We don't have to do anything special wrt to the sandbox as it won't affect the > migration logic (just tested). > > The flatpak version of gnucash will still search for the old configuration in > $HOME/.gnucash (that is, not sandboxed) > It will migrate this to locations inside the sandbox though. So make sure the > following locations don't exist if you want the migration to be triggered: > $HOME/.var/app/org.gnucash.GnuCash/data/gnucash > $HOME/.var/app/org.gnucash.GnuCash/config/gnucash > > Regards, > > Geert > > _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
