2015-06-25 11:00 GMT+02:00 Simon McVittie <[email protected]>: > The commit message for data/blakestone.yaml says "WIP". Do you consider > this to be ready for release, or should I disable it for g-d-p 42?
G-D-P already support the one version (to be) supported by ecwolf. What remains to be done is locating v1.00 & firing-up DOSBox to apply the patches one by one to get the checksums of all intermediate versions and tag them as "unsuitable". (or get someone to reverse-engineer patch.exe) So support for this get is not yet optimal, but already pretty good, especially for Steam or GOG that both ships now latest version. I can finish this soon. > Do we want to disable the generation of these packages until a suitable > ecwolf exists, at least upstream? That's what I was thinking of when I added is_available(); this is better than having a flag in the yaml file; because this got evaluated a run-time, and then there is no hurry to release a new GDP each time a new engine lands in the archive. And this also recognize the .deb's provided by upstream game engine projects. Disabling it completely seems a bit too much; maybe showing a warning and/or a confirmation prompt would be more appropriate, and/or just always enable those if DEBEMAIL is set ? There are tens of half-done engine recreations that could be added to GDP to eventually help their development. https://en.wikipedia.org/wiki/List_of_game_engine_recreations Alexandre -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
