Bug 244369
| Summary: | emulators/i386-wine-devel: update to 5.2 | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Nikita Stepanov <nikitastepan0v> |
| Component: | Individual Port(s) | Assignee: | Lorenzo Salvadore <salvadore> |
| Status: | Closed Overcome By Events | ||
| Severity: | Affects Many People | CC: | Alexander88207, gerald, iwtcex, lehmannwer, sv |
| Priority: | --- | Flags: | salvadore:
maintainer-feedback+
|
| Version: | Latest | ||
| Hardware: | amd64 | ||
| OS: | Any | ||
| Bug Depends on: | |||
| Bug Blocks: | 244547 | ||
|
Description
Nikita Stepanov
2020-02-24 14:33:38 UTC
If that's a request for updating i386-wine-devel, it's coming. We are know working on improving the port management (Makefile style and similar things): once we are done with that we will update the port. Great news, thank you! I know it's not exactly the right place to ask, but what is the status of wow64 with FreeBSD? Am I right to assume that once that will be achieved, there will be no more need for i386-wine? (In reply to Werner Lehmann from comment #2) At the moment we are not working on wow64. Improving and updating existing wine ports is a complex task and it will take some time. Once this is done, next step will probably be wow64. Some attempts to implement it have already been done and they might be used as starting points. You can get more information from the following links: - https://www.freebsd.org/news/status/report-2019-10-2019-12.html#Wine-on-FreeBSD (see also future quarterly status reports); - https://reviews.freebsd.org/D14721 ; - https://reviews.freebsd.org/D16830 ; - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242625 . As for your assumption I think you are right: if you install wow64 you do not need i386-wine. However, this does not necessarily means that we will deprecate i386-wine. I did not study wow64 much yet, since I am focusing on improving and updating the existing ports, but this is how I understand things for now, assuming we are looking at an amd64 machine: - wine runs 64-bit applications; - i386-wine runs 32-bit applications; - wow64 would run both 32-bit and 64-bit applications. If we deprecate i386-wine we make impossible for users to install something that runs 32-bit applications but do not run 64-bit applications. This might be a problem, for example if wow64 package gets particularly big or for security reasons (user becomes vulnerable to any security issue in the 64-bit part of wow64 although (s)he do not need it). Feel free to mail me for more information if you want: that's one of the reason we include a MAINTAINER field in all of our ports ;) (In reply to Werner Lehmann from comment #2) > I know it's not exactly the right place to ask, but what is the status of wow64 with FreeBSD? WoW64 itself works just fine. Apparently since 2015 (!). Nothing, absolutely nothing prevents you from building it. The corresponding Wine ports are stuck with some really unfortunate compromises, which make it rather inconvenient to provide WoW64-enabled packages. By the way, I just remembered giving a build-i386-wine-quick advice (to the same person) at https://bugs.winehq.org/show_bug.cgi?id=40990#c15. We are going in circles. (In reply to Lorenzo Salvadore from comment #3) > Improving and updating existing wine ports is a complex task > and it will take some time. Can you speed it up a little? Prioritizing Makefile cleanup over immediate issues doesn't seem that wise. (In reply to Alex S from comment #5) I will do my best to speed up things. To say the truth, the cleaning patch is fully ready, however the complexity of the wine ports requires us (gerald and me) to commit it piece by piece. Moreover things are slowed down by the fact that I am a mentored committer instead of "full" comitter, so every commit on my part needs approval before being done. Please be patient, I assure you we are working much on the wine ports and we do not neglect them. The port has now been update to 5.5. |
