On 02/12/13 19:34, Helmut Karlowski wrote:
Alan Hourihane, 12.02.2013 20:19:42:On 02/12/13 18:54, Helmut Karlowski wrote:Alan Hourihane, 12.02.2013 18:43:45:There are some binary only modules out there which would be subject to this shared mode I guess.Not only binaries, also a "shared" solution would be necessary for data-files like rsc, img, some common config-stuff and maybe moreShared solution for non-binary files makes sense to the point of version match. i.e. c:\mint\1-19-0\... and below. It doesn't make sense to go higher than that and try and load shared non-binary files from c:\mint\ as RSC files etc can change between versions.For XaAES this would not be a problem: it manages rsc-versions separately - different versions can reside at the same place. Also the background-images could go into c:/mint/..., it would waste a lot of space and be quite uncomfortable to maintain them for each version/machine.
Can you explain how XaAES manages rsc-versions ?
Maybe this project needs some refinement of how "shared" something should be -global: mint/, version: mint/<ver>, machine: mint/<ver>/<mch> ? But this might also become quite confusing.
This is what Miro has extended to already. The "global" and "version" already exists today, Miro has just added "machine".
Alan.