Le 22/09/2021 à 17:35, Clément David a écrit :
Hi Stéphane, hi Samuel, hi all,
The idea behind SCIHOME is to have a version specific directory to
avoid any issues when upgrading from Scilab versions to Scilab
versions ; IMHO implementing an upgrade for files stored into this
directory is for me a non-sense ; the upgrade could be done manually
(as Samuel described) for the few users that copy the files between
SCIHOMEs.
IMHO, having a separate SCIHOME directory for each scilab version is fine.
This does not necessarily demand to initialize SCIHOME configuration
files with "factory files" shipped with the release, at the first run,
as it is currently done.
This initialization could be done with configuration files of a previous
most recent Scilab release, provided that configuration files are tagged
with the scilab version that generated (or upgraded) them as proposed by
Stephane.
This would improve the continuity of usage.
However, detecting a previous version on the same computer is not so
obvious.
Currently, scilab user preferences are not extremely numerous, and as
long as scilab releases won't be more frequent, resetting preferences by
hand for each release is feasable and not blocking.
But for softwares and freewares that propose frequent upgrades, handling
the copy or upgrade of configuration files in an automatic way is just
mandatory.
Samuel
PS: by the way, i thing that, as a general rule, tagging a generated
file with the (name and) version of the software that generated it is
wise and dramatically improves files backward compatibility. This could
be done as well for .scg files (i don't thing they are tagged), .zcos
files (may be they already are), . dat ones (from save()), etc.
_______________________________________________
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users
