#40315: grass: tries to load wx despite --disable-wxwidgets ----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: grass | ----------------------+-------------------------------- Comment (by mojca@…): In r116076 I changed the port in such a way that it depends on wxWidgets no matter what. If anyone really needs the software without any GUI, we can look at this again. It's probably still worth submitting a bug report upstream if anyone cares enough, but in it's current form it doesn't affect the port in MacPorts any longer. Just to answer the last questions: Replying to [comment:6 egall@…]:
- Why is the wxWidgets PortGroup used outside of the `+wxWidgets` variant?
Because it doesn't matter. The PortGroup itself doesn't do any modifications and doesn't change the port in any way. One needs to explicitly use {{{ wxWidgets.use wxWidgets-2.8 }}} to restrict the set of platforms or throw an error when incompatible platform is used for example. And dependencies need to be added explicitly.
- Why is `wxWidgets.use` set to `wxPython-3.0` outside of the `+wxPython` variant?
Same as above: because it doesn't matter until one actually uses {{{ depends_lib-append port:${wxWidgets.port} }}} but I changed that last part in r116076 where two different versions are supported. -- Ticket URL: <https://trac.macports.org/ticket/40315#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X