That's is a good point!
I'm considering to refine the packaging in the future.
Currently we have a single package 'basex', that provides four commands 'basex,
basexgui, basexclient, basexserver'.
In one of the next packaging cycles, I like to change this to something like:
• a core 'libbasex-java' package
… and packages that depend on libbasex-java, each using it in a special way.
• 'basex' - console standalone package
• 'basexgui' - graphical standalone
• 'basexserver' - database server, here a unix-like /etc/init.d script could be
placed in
• 'basexclient' - database client
• 'basexhttp' - restxq facade in front of basexserver using jetty://
Let's see what time permits.
Cheers,
Alex
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
