Re: [basex-talk] Unable to Make My Custom EXPath Module Work

How best to manage deployment of XQuery modules and top-level scripts from a source environment to a running remote server so that using scripts can import modules using just the module namespace?

If you don’t care about version conflicts and other potential dependency errors, you could use the following expression (the argument of fetch:binary can be an arbitrary URI):

basex "archive:extract-to(db:option('repopath'), fetch:binary('....zip'))"

I looked quickly at the code for EXPath package processing but I didn’t spent much time in it, but it probably wouldn’t be too hard to enhance it to behave as I expected. I could possibly pursue that if anyone else would use it.

Thanks for the offer, that would certainly be appreciated.