posted by Paul Libbrecht at Nov 30, 2007 4:43 PM
Quote
Not that I want to… at least I haven't figured out if I want it.
I just do not want to care about it…
Fine then! Things are getting greater every day.paul
posted by Sebastien Jourdain at Nov 30, 2007 4:28 PM
Quote
Yes you can do what ever you want. But when we say that the topology need to be like a tree, is to unsure convergence with few conflict.
The thing that can create conflict easily is making loops… And do commit/update without thinking...When you know what your are doing, you can make loop. But then, you should explain to me why you needed to make a loop…
posted by Paul Libbrecht at Nov 30, 2007 3:25 PM
Quote
So, that's amazing, that'd be a way to create arbitrary topologies of repositories, including workspaces that pull from three or four queues… is that correct ? Papers about so6 tended to say that the topology had to be a tree...paul
posted by Sebastien Jourdain at Nov 30, 2007 9:22 AM
Quote
Create a workspace in a directory A with the synchronizer 1, and Create a new workspace in the SAME directory A with the synchronizer 2.
Then, you will have on your computer a workspace that will allow you to filter and propagate data from one synchro to another...Regards,Seb
posted by Paul Libbrecht at Nov 29, 2007 11:29 PM
Quote
Hello LSers,I am more and more enthusiastic of libresource. Last experience was with a non-techie and I almost had full adoption! See my blog post.In order to fullfill a "rich upload mechanism", I would like to use this ability of the Libresource synchronizer to cascade. So I was expecting to be able to create queue within the project (a synchronizer maybe?) and let this one actually be a workspace of another queue somewhere else.An example of such, would be if we had a team of developers working on the libresource server software here and we wanted to share internally the result before committing it.How do I start this ?thanks in advancepaul