[MacPorts] #56143: wine{, -{devel, crossover}}: new +universal woes

[MacPorts]

#56143: wine{,-{devel,crossover}}: new +universal woes
---------------------------------------------+----------------------
  Reporter:  Ionic                           |      Owner:  raimue
      Type:  defect                          |     Status:  assigned
  Priority:  Normal                          |  Milestone:
 Component:  ports                           |    Version:
Resolution:                                  |   Keywords:
      Port:  wine wine-devel wine-crossover  |
---------------------------------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:9 Ionic]:
 > > Yes, doing it only when the universal variant is not set might work.
 >
 > Might,

 I am testing it now.

 > but then again would leave us with the "logical dilemma" I mentioned in
 the report - for wine ports, the behavior of `+universal` would be
 reversed compared to all other ports. I don't feel too comfortable with
 that, but it's the maintainer's decision in the end.

 I am not terribly concerned about it. There are two valid builds of wine:
 32-bit only, and 32-bit-and-64-bit. Using the universal variant for this
 is slightly weird, but wine itself is more than slightly weird anyway.


 > Maybe we shouldn't use `universal` here at all, but rather introduce new
 `win32` and `win64` (or `wine32` and `wine64`) variants that enable
 building a specific variant, irrespective of the machine's base arch. Do
 we actually need `muniversal` and merging here? Wine normally adds
 postfixes to its 64bit variant binaries. Libraries will need to be staged
 into different directories (and we should make sure to tell wine where to
 find those in the build process), but I don't think that `muniversal` is
 actually useful here. We don't want to actually merge thin binaries into
 fat binaries. We already stage stuff into different directories via the
 `dlldir` override.

 There is extensive discussion about how the 64-bit support was added to
 wine in the previous ticket and PR. I deliberately stayed out of the
 discussion because I did not want to take on the responsibility. I left it
 to someone else to decide what to do. And it was done, and they thought it
 worked.

--
Ticket URL: <https://trac.macports.org/ticket/56143#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS