Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Bo Berglund wrote: > But could one not do the following: > Modify the Entries file (or the Entries.Extra) to hold the name of the > file *and* the physical server side path to it. Then updates need only > bother with Root and Entries.Extra to know where to turn to on the > server. And one could handle the case where several files from > different server folders wind up in the same client folder. cvs as it is simply couldn't support that - it's directory based, so everything has to come from the same directory otherwise it won't work. > Another observation: > When a virtual module is checked out there is no info stored about > this so it is not possible to update with this info in mind. Therefore > changes to the virtual module definition will not be reflected in the > sandbox unless a new checkout is done. With physical modules this is > not the case of course. > Is there any way to solve this (modules2 for instance)? The new core is all virtual, so something like that could work (but of course that won't be ready for a while). The way modules works at the moment though means there can't be any record of the module as the information is lost fairly early in the checkout. modules2 was supposed to handle that, and does for simple cases, but once you get into the complex stuff it breaks down (basically down to the complexity of converting logical->physical->logical about 3 times that the current core requires... hence the need for the rewrite, which never uses physical paths at all until it actually fetches the file). Tony