[MacPorts] #58666: py36-pyside2 - problem with pyside2-rcc

[MacPorts]

#58666: py36-pyside2 - problem with pyside2-rcc
-------------------------+----------------------
  Reporter:  cainesi     |      Owner:  pmetzger
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.5.4
Resolution:              |   Keywords:
      Port:  py-pyside2  |
-------------------------+----------------------

Comment (by cainesi):

 I think I have figured out the problem.

 1) build_scripts/config.py (around line 200) defines entry points for
 pyside2-uic, pyside2-rcc, and pyside2-lupdate.  I assume the
 python.versions variable in the portfile causes appropriately renamed
 versions of those entry points (i.e., appending "-3.6" or whatever) to be
 put in the Macports bin directory.

 2) The entry points for rcc and lupdate are a bit funny--they do not
 actually point at python files that implement the relevant commands.
 Instead they point at pyside_tool.py.  What that script does is look at
 sys.argv to figure out what command was invoked, and then tries to run an
 executable file with the same name in a certain directory.  I.e., it
 relies on the name of the file where the entry point is invoked being the
 same as the name as the executable that is supposed to be run (seems like
 a fragile approach...). This is broken by the renaming that happened in
 item 1 above.  (pyside2-uic-py36 does not go through pyside_tool.py and
 does not have this problem).

 Not sure what the best way to fix this is?  I suppose we could just
 replace pyside2-rcc-py36 and pyside2-lupdate-py36 in bin with links to the
 relevant executables?

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