Hi Ceel,
Thank you for all your reports!
Yes, I know I fix bugs very slow. Actually, I rewrite and adopt parts of TazPkg. So, real debugging is soon. I think, I'll show beta version of the new TazPkg on the next week.
Why I started to rewrite the code? Because it very large and hard to understand — as well as to implementing new features and debug. So, I broke single tazpkg script into number of independent modules — it is often one module per tazpkg command. So, if command that shows package info (for example) not works — then we should find bugs only in the module 'info'. Next, if I want to make new feature for working with cache — not only to remove all packages but, say, remove only installed and leave not-installed — then I'll touch only 'cache' module and will not to add new bugs to other modules and commands.
Now I working with the heart of TazPkg :) It is module 'get-install' to get and/or install packages. This module is significantly bigger than others — about thousand lines of code (both with depending functions). Work in progress, and I planning to finish this part on the next week.
I can't push current code into SliTaz Hg because currently this code broken and it will not work.
It is question still stay opened — what about other SliTaz tools/services? Can 'root' support, for example, to break SliTaz service that make weekly ISOs?
I know, changes are huge. But, frankly, TazPkg was very hard to maintaining. And here no way back, only forth! :)
And finally, touching your last question. No, it is not normal. Please, see tazpkg script — here for reference
http://hg.slitaz.org/tazpkg/file/a02e36d44d06/tazpkg#l1459
In the line 1459 please quote with single quotes part of the line:
'*.tazpkg'
This should help.
And now I have this code in the 'cache' module, and this code is slightly different.
That's all for the moment :)
Have a good day!