Hi Samuel,
Thanks. I will try your suggestion when I update the file with the same version
number next time.
Currently any changes I did I would create a new subversion for it, or just a
small patch file. I was thinking it could be just mentioned as "SOP" instead of
reporting as a bug.
Will keep you posted on this.
Regards,
Chin Luh
---- On Wed, 20 May 2020 23:11:59 +0800 Samuel Gougeon
<mailto:[email protected]> wrote ----
Hello Chin Luh,
Le 20/03/2020 à 15:36, Chin Luh Tan a
écrit :
Hi,
There is a little issue always bugging me, whenever an
atoms module has been installed, it will be kept in "archives"
folder, either in SCI or SCIHOME respective folder.
Under some circumstances if the developer update some patch
in the portal and and remain the same version,
atomsSystemUpdate followed by atomsInstall the module will
pick up the archived module instead of the latest one from the
web. User need to manually delete them from the folder in
order to get the latest one.
Is there any function in atoms* which I might have miss out
which could clear the archives? It sounds redundant to
developers or advance user but it makes sense for normal
Scilab user.
Have you tried to run atomsUpdate(your_module) instead of
atomsInstal(your_module), in addition to atomsSystemUpdate()?
If it does not work better, it would be worth reporting the issue on
bugzilla.
Best regards
Samuel
_______________________________________________
users mailing list
mailto:[email protected]
http://lists.scilab.org/mailman/listinfo/users_______________________________________________
users mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/users
