Now, I really feel it's a pity that you can't checkout. It means, thus far, that in oder to checkout a collection on our server I need to connect through X-Windows to that server, open a browser, launch a JNLP, that'll create the workspace. With the X-server on MacOSX that has severe issues (don't ask me why, it's the same for the LS-installer).

Instead, for subversion or cvs, I issue a single command-line. Why not consider implementing that?

thanks in advance

paul]]> http://dev.libresource.org/home/community/forum/so6_CLI_to_checkout_/RE_so6_CLI_to_checkout_ Sebastien Jourdain 2008-02-07T09:35:11+01:00 libresource workspace from the command line. The createWorkspace command line will link the workspace to a filesystem synchronizer.

But you can update and commit any existing workspace.

The other thing is, I'm not sure that you don't need a bigger classpath. (Check the JNLP file when you create a workspace from the web)]]> http://dev.libresource.org/home/community/forum/so6_CLI_to_checkout_/so6_CLI_to_checkout_ Paul Libbrecht 2008-02-06T23:54:49+01:00 I'm a bit puzzled with the So6 jar command-line interface.

I would like to checkout a queue at: ls://ls.activemath.org/projects/i2gOntology/src but… when I use:

so6 createWorkspace `pwd` ls://ls.activemath.org/projects/i2gOntology/src "paul-second" then so6 update -w `pwd`

all it does is create a bunch of nested directories (ls:/ls.activemath.org/projects/i2gOntology/src/) whereas I'd expect the queue content.

The cli-interface suggests to use: so6 command in order to be enlightened on the cli-usage but that didn't help… it says:

createWorkspace workspacepath queuepath workspacename Exemple: so6 createWorkspace ~/foo ~/queue1 "seb loria"

but that queue name seems to be a local thingie...

paul]]>