Sorry for taking so long to answer, I struggled to get Internet access before.
First point: I would prefer patch instead of commits for testing/unfinished features
![Smile :)](./images/smilies/icon_smile.gif)
I must demonstrate the engine in the next two days, and I would very embarrassed if something goes wrong !
![Smile :)](./images/smilies/icon_smile.gif)
I may have said this before, but let's consider that the SVN trunk must remain stable.
Small points about the commits:
- a few typos in docs (seen "spécify", "paclage") that perhaps needs a last "re-read". For instance, I've not seen information about the default mode for a zip ? Other example: raydium_path_package_register() still states that zip can't be modified ... I think we can remove this, no ? Always for this function, we could perhaps repeat the default priority ?
- logs in path.c ("********* Path package update", ...) not relevant ? IMHO "'xxxx.xx' added to 'yyy.zip'" is enough.
- raydium_path_package_mode() is declared as "signed char" but returns nothing ?
Big points about the feature and the test:
./odyncomp.sh test6.c --package zipfile.zip
... tries to download zipfile.zip -> not found -> empty file (not created on the disk).
console : raydium_path_package_mode("zipfile.zip",RAYDIUM_PATH_PACKAGE_READWRITE);
when I quit: creates zipfile.zip and fills it with files. Seems ok to me.
BUT the readwrite flag is not added to the file ! (even if the console said it is when I quit)
So when I relaunch the application, package is set to readonly.
Another thing (perhaps related), when I launch again the application and the set the mode "again" to readwrite, when I quit, it "rebuilds" again the zip file even if the files inside are the same.