[GNC] Upgrade Path from version 2.6.16 on MacOS High Sierra (10.13.6) and beyond

[John Ralls]

> On Jan 29, 2019, at 8:24 AM, Geert Janssens <geert.gnucash at kobaltwit.be> wrote:
> 
> Op dinsdag 29 januari 2019 17:19:59 CET schreef John Ralls:
>>> On Jan 29, 2019, at 8:03 AM, Geert Janssens <geert.gnucash at kobaltwit.be>
>>> wrote:> 
>>> Op dinsdag 29 januari 2019 15:28:01 CET schreef Adrien Monteleone:
>>>>> I'm curious: what are the names of the two directories that were created
>>>>> ?
>>>>> Or in other words, how are those names decided on MacOS ?
>>>>> 
>>>>> As far as I know on linux and Windows the names are hardcoded to use the
>>>>> compile time application name unless overridden by setting GNC_DATA_DIR
>>>>> and
>>>>> GNC_CONFIG_DIR environment variables. The latter (GNC_CONFIG_DIR) is
>>>>> only
>>>>> introduces in GnuCash 3.4.
>>>>> 
>>>>> Geert
>>>> 
>>>> The names matched the app name. (not including the .app extension of
>>>> course)> 
>>> App name as in "GnuCash" and "GnuCash-2" as in your earlier example ?
>>> That's interesting but puzzling as I don't see anything in the code that
>>> would make that happen. The default directory is hardcoded to GnuCash as
>>> of gnucash 3.x.
>>> 
>>> Perhaps John does some magic to change this in the MacOS integration repo.
>> 
>> Nope, and as far as MacOS is concerned the "App Name" which appears at the
>> left side of the menu bar and in Activity Monitor is "Gnucash", the name of
>> the executable in Gnucash.app/Contents/MacOS that's named in
>> Gnucash.app/Contents/Info.plist. The filename of the bundle (i.e.
>> Gnucash.app or whatever the user might rename it to) doesn't matter to
>> anything except the file system.
>> 
>> Regards,
>> John Ralls
> 
> Ok, that's how I understood as well. So I can only assume the two application 
> data directories are "GnuCash" and "Gnucash" (different capitalization of the 
> letter "C").
> 
> For 2.6 this directory was called "Gnucash" and in the 3.x series I renamed it 
> to "GnuCash". That was under the belief that MacOS' file system was still 
> case-insensitive/case-preserving so it would be an innocent no-op for most 
> users. IIRC you recently told me it no longer is so this will affect people 
> migrating to a more recent gnucash version.

It's still true by default. Users have always had the option of making HFS+ and APFS filesystems case-sensitive at creation (i.e. format), but few do.

Regards,
John Ralls