or to something else.
You can change default directories in function boost::filesystem::path GetDefaultDataDir(){..}
https://github.com/Bitcoin-ABC/bitcoin-abc/blob/master/src/util.cpp#L470
to something like - "bitcoinabc",
original lines -
// Windows
return GetSpecialFolderPath(CSIDL_APPDATA) / "Bitcoin";
// Unix
return pathRet / ".bitcoin";
to
return GetSpecialFolderPath(CSIDL_APPDATA) / "BitcoinAbc";
return pathRet / ".bitcoinabc";
etc.
Yes, I want to do that at the same time we change the magic. So the software will be able to take existing data in .bitcoin and dump them in the new folder with the new magic. Doing both at once will limit disruption.
Do you like you could solve that problem by using a sym links or an install script of some kind, on osx it just destroys any existing core clone setup by using all the same paths and binary names. On a unix release it required some creative re-naming of the binaries then a bit of sym link setup to the existing block core directory structure.
The ABC client should not use the same data directory as another which may want to change their data format or even move their data to another location. Such symlinking may be adequate to do as a resource-saving measure for a personal installation, but it is not suitable as a safe way of wide deployment.
Where conflicts with existing installed software exist they should be resolved such that ABC can be operated independently, and data migrations steps offered to the user where possible.
Duplicate of #141
Most helpful comment
Yes, I want to do that at the same time we change the magic. So the software will be able to take existing data in .bitcoin and dump them in the new folder with the new magic. Doing both at once will limit disruption.