List latest Wine engine releases in when adding new engines to Winery

[marnovo]

Feature request:

Wineskin Winery should automatically list the latest Wine engines available for macOS in the list of available engines whenever you are adding a new Wine engine to the Wineskin Winery application.

Thank you for supporting this project.

[Gcenx]

When the project is ready it will have all usable engines available via Winery.app

But that also requires hosting & hosting costs for said engine files the real release can not do what I'm currently doing with my unofficial update since Github limits to 1GB of space.

[marnovo]

@Gcenx thanks for the prompt reply! Couldn't you rely on the listing/hosting from the WINE project itself?

By the way, I have a small tutorial on how to add a new engine to the list manually.

[Gcenx]

@marnovo there is already a tool to package the wine versions into engines under the Wineskin Community repot.
It's based on your code that you linked btw

I guess technically it could just download Wine and repack it directly but that does not help for things like WineCX engines and keeping support for OSX10.6, so prepackaged engines would be best in those cases

[Gcenx]

@vitor251093 I keep thinking about the idea of Winery downloading the pre-build Wine builds and just packing them into Engines and only hosting things like WineCX engines?

[chrisballinger]

that makes sense to me

…

On Fri, Jul 6, 2018 at 8:06 PM Gcenx ***@***.***> wrote: @vitor251093 <https://github.com/vitor251093> I keep thinking about the idea of Winery downloading the pre-build Wine builds and just packing them into Engines and only hosting things like WineCX engines? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAfqHx7iHnzDyTfLYWm8IJHE2YlQwyO2ks5uECWcgaJpZM4U-heA> .

[vitor251093]

It makes sense for me as well.

Although, since we already very close to a stable version at the moment, I think we can leave that for the second version ;)

By the way, talking about versioning, @chrisballinger do you have any recommended versioning system?

[chrisballinger]

I like using something like semver: https://semver.org/

major.minor.patch

[marnovo]

+1 to semver.org (not that you asked me, anyway) :)

[vitor251093]

Nice :D

Considering that the minor and the patch versions require the update to be backwards-compatible, and if we want to adopt it for good, I think the best way to start the first release would be with Wineskin Winery 2.0 (prior official version was 1.7) and Wineskin App 3.0 (prior official version was 2.6.2).

Everyone agrees with that?

@marnovo lol, sorry for almost ignoring you in your own issue xD

[Gcenx]

Agreed

[chrisballinger]

Aye

…

On Sun, Jul 8, 2018 at 3:28 PM Gcenx ***@***.***> wrote: Agreed — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAfqH8VXUDguP0v3da9K-5HnlH0OkWYtks5uEoekgaJpZM4U-heA> .