[MacPorts] #52278: minivmac @3.2.3 needs some trickery to find and use ROM...

[MacPorts]

#52278: minivmac @3.2.3 needs some trickery to find and use ROM...
--------------------------------------+--------------------------------
  Reporter:  ken.cunningham.webuse@…  |      Owner:  macports-tickets@…
      Type:  defect                   |     Status:  new
  Priority:  Normal                   |  Milestone:
 Component:  ports                    |    Version:  2.3.4
Resolution:                           |   Keywords:
      Port:  minivmac                 |
--------------------------------------+--------------------------------

Comment (by ryandesign@…):

 Thanks for the compliments! It's been complicated, ever since the Mini
 vMac build system became self-hosted in version 3. I've had a lot of back
 and forth with the developer over the years, and he's made a few changes
 to better accommodate our automated builds, which finally landed in Mini
 vMac 3.3, which has been a development release for awhile, but was only
 just promoted to a stable version and I haven't had time to update the
 minivmac port with that yet. Until I do, please use the minivmac-evel port
 instead.

 Mini vMac is supposed to allow the ROM file to be in several locations,
 but I think I ran into permissions problem as you did with recent MacPorts
 / macOS versions when trying to put it in my home directory. I've had the
 best success just putting it in the same folder as the app
 (/Applications/MacPorts/Mini vMac) so that's what I do now and what I
 recommend.

 You can build custom versions of Mini vMac if you're willing to edit the
 portfile and add your own variants. I intend to make this easier, where
 you could write a config file for each custom build you want and the
 portfile would read it.

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