Andreas Poisel wrote:
> Just one minor issue: starting with a 0.9pre release (if I remember
> correctly) the MakeAppWorkDir.py script refused to write the application
> skeleton when the target directory already existed.
> I used to check out e.g. the "MyApp" directory from version control and
> webware-ify it with "MakeAppWorkDir.py MyApp" afterwards.
I have usually checked in everything that is needed (directory
structure, config files and launcher), so that it runs out of the box
without the need to "webware-ify" anything. This is not much overhead
and it makes sense to save the config files anyway.
> This doesn't work anymore, is there a specific reason for this behaviour?
> I've no problem working around this issue, but I don't like constraints
> without having a decent motivation... ;-)
I can allow running on an existing working dir, but how should
MakeAppWorkDir behave if the config files or the launcher script already
exist? Overwrite or keep (there could be some customization in the
config files and launcher script already)? Maybe we can add an option
--overwrite, but what should be the default?