Am 24.04.2014 16:33, schrieb Rikki Cattermole:
On Thu, 24 Apr 2014 14:06:29 GMT, Sönke Ludwig wrote:
Unfortunately I can't really invest time for this at this point (although it's an interesting topic), but for the specific case of dynamically reloading Diet templates there has been a short thread a while ago. But one thing that will always be an issue is of course when data types get changed and thus existing memory structures get invalidated. For this reason I'm not entirely sure if this should be endorsed as a standard tool for the average library/framework user who may not be aware of such traps.
I'm okay in the case of Cmsed as I can make sure what data is registered will be deregistered. But I see your point in the general case.
As far as getting what I need to do this, how would you feel about a copyDirectories option? Its far from what I could use, but atleast I wouldn't have to write a new build manager.
I'll implement a way to access the directory of individual packages with $variables in "postBuildCommands" and similar fields, which can then
be used with cp -r to achieve this. Instead of a simple
"copyDirectories", I'd like to implement something more powerful and
with better semantics at some point, but that still needs some thought.