Hi,
As I really don’t want to have to ‘manually’ install Draft on 200+ machines, I assume I can just overwrite the existing \repository\bin\windows\draft directory structure and add some ‘text’ to the “version” file to force a system wide upgrade?
Personally, I think you should leave Draft in the main installer package as I thought its meant to be available for anyone on Deadline subscription and of course, the flexlm licensing system takes care of controlling who can use it or not.
The biggest Draft payload looks like the Mac at about 11Mb which isn’t really that big given the 500GB drives or more, people have these days. I totally understand the Python removal but Draft as well? I thought it would be nice to encourage people to use this new system by making it ‘eval’ friendly and available by default in Deadline?
Thanks,
Mike
+1
Yes, that should work; we probably should have mentioned that. 
As for our reasoning behind the separate Draft download, it’s just something we were wanting to try out. We figured the bonus of being able to roll out new Draft versions separate from Deadline would be benificial, since we wouldn’t have to wait for the next Deadline build to fix issues with Draft, or vice-versa. Plus, bundling all the Draft builds in the repo installer adds an extra 40mb to the download, which isn’t totally insubstantial; especially since some people aren’t planning on taking advantage of Draft.
I think for actual releases though (and maybe for the rest of the beta also, since you guys seem to prefer having it bundled ), we might go back to bundling it in the installers, if only to ensure its availability.
Thanks for the input as usual guys!
Cheers,
- Jon