So far, I am only worrying, and maybe without reason.
But I experienced that the Ryzom installation, as performed during the transition from 2.x to 3.x clients, disperses files and directories over the file system hierarchy, here and then creating issues under windows (especially, but not exclusively XP), and linux distros with file system design different from Ubuntu.
Worst are assumptions that core parts of the installation have to be located under /home/<user>/something or /{users|staff|wheel|..}/<user>/.. etc. under linux, and c:\users\<user>/something, hierarchies nonexistant under e.g. linuxes with /export/home/<user> design or windows where the ..\<user> is residing elsewhere. Maybe this is resolved over a $HOME variable or so, but still shaky.
Some Ryzomers love to compare and experiment, or prefer portable ryzom instances located on SD cards, USB sticks, or external disks. In that case, the isolated runnable Ryzom inside a single directory under which everythin resides is essential. If you are using your shop's laptop for professional work, your IT security may be somewhat unhappy when finding C:\Appdata\<youruser>\Ryzom stuff on your box while plugging an external USB3 disk (even USB2 is running fine) after work hourse would not be a problem.
I recognize the wish to facilitate installation of a single Ryzom instance parts of which are located in the individual user's space on the box. But the isolated one folder solution must not be abandoned.
But I experienced that the Ryzom installation, as performed during the transition from 2.x to 3.x clients, disperses files and directories over the file system hierarchy, here and then creating issues under windows (especially, but not exclusively XP), and linux distros with file system design different from Ubuntu.
Worst are assumptions that core parts of the installation have to be located under /home/<user>/something or /{users|staff|wheel|..}/<user>/.. etc. under linux, and c:\users\<user>/something, hierarchies nonexistant under e.g. linuxes with /export/home/<user> design or windows where the ..\<user> is residing elsewhere. Maybe this is resolved over a $HOME variable or so, but still shaky.
Some Ryzomers love to compare and experiment, or prefer portable ryzom instances located on SD cards, USB sticks, or external disks. In that case, the isolated runnable Ryzom inside a single directory under which everythin resides is essential. If you are using your shop's laptop for professional work, your IT security may be somewhat unhappy when finding C:\Appdata\<youruser>\Ryzom stuff on your box while plugging an external USB3 disk (even USB2 is running fine) after work hourse would not be a problem.
I recognize the wish to facilitate installation of a single Ryzom instance parts of which are located in the individual user's space on the box. But the isolated one folder solution must not be abandoned.
---
Daomei die Streunerin - religionsneutral, zivilisationsneutral, gildenneutral