[MacPorts] #46856: add xvfb support to xorg-server package for proposed xvfb-run package to use
#46856: add xvfb support to xorg-server package for proposed xvfb-run package to use -----------------------------------+-------------------------------- Reporter: howarth.at.macports@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: xorg-server -----------------------------------+-------------------------------- The attached Portfile diff implements a new xvfb subport to provide the missing Xvfb for the new proposed xvfb-run package to use. -- Ticket URL: <https://trac.macports.org/ticket/46856> MacPorts <https://www.macports.org/> Ports system for OS X
#46856: add xvfb support to xorg-server package for proposed xvfb-run package to use ------------------------------------+-------------------------------- Reporter: howarth.at.macports@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: Port: xorg-server | ------------------------------------+-------------------------------- Comment (by howarth.at.macports@…): The post-destroot of the new xvfb subport removes files installed by the build which overlap with the main xorg-server package; -- Ticket URL: <https://trac.macports.org/ticket/46856#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#46856: add xvfb support to xorg-server package for proposed xvfb-run package to use ------------------------------------+------------------------ Reporter: howarth.at.macports@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xorg-server | ------------------------------------+------------------------ Changes (by larryv@…): * cc: jeremyhu (removed) * owner: macports-tickets@… => jeremyhu@… * version: 2.3.3 => -- Ticket URL: <https://trac.macports.org/ticket/46856#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#46856: add xvfb support to xorg-server package for proposed xvfb-run package to use ------------------------------------+------------------------ Reporter: howarth.at.macports@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xorg-server | ------------------------------------+------------------------ Comment (by jeremyhu@…): Why do you care about Xvfb? It's *super* deprecated. I'd much rather see you use Xorg with xf86-video-dummy -- Ticket URL: <https://trac.macports.org/ticket/46856#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#46856: add xvfb support to xorg-server package for proposed xvfb-run package to use ------------------------------------+------------------------ Reporter: howarth.at.macports@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xorg-server | ------------------------------------+------------------------ Comment (by howarth.at.macports@…): See Ticket #46857. How do I execute the equivalent of... system -W ${worksrcpath} "`which xvfb-run` ${prefix}/bin/R CMD INSTALL -l pkg --byte-compile --build ${distpath}/[lindex ${distfiles} 0]" using xf86-video-dummy? Do we have to totally rewrite the debian xvfb-run to use xf86-video-dummy or does xf86-video-dummy provide its own run script? -- Ticket URL: <https://trac.macports.org/ticket/46856#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#46856: add xvfb support to xorg-server package for proposed xvfb-run package to use ------------------------------------+------------------------ Reporter: howarth.at.macports@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xorg-server | ------------------------------------+------------------------ Comment (by jeremyhu@…): Why do you need an X11 server at build time? That seems like an obvious bug in the build system to me. -- Ticket URL: <https://trac.macports.org/ticket/46856#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#46856: add xvfb support to xorg-server package for proposed xvfb-run package to use ------------------------------------+------------------------ Reporter: howarth.at.macports@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xorg-server | ------------------------------------+------------------------ Comment (by jeremyhu@…): We can discuss that in #46857. As for this, I think I'll do it a tad differently but I'll get something like it in soon. -- Ticket URL: <https://trac.macports.org/ticket/46856#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#46856: add xvfb support to xorg-server package for proposed xvfb-run package to use ------------------------------------+------------------------ Reporter: howarth.at.macports@… | Owner: jeremyhu@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: xorg-server | ------------------------------------+------------------------ Comment (by howarth.at.macports@…): Replying to [comment:5 jeremyhu@…]:
Why do you need an X11 server at build time? That seems like an obvious bug in the build system to me.
The X11 accesses arise from the byte-compilation of the R code in rNMR.r during the execution of the R CMD Install command. I believe this is the nature of the beast and you really can't work around it short of resorting to xvfb-run or its equivalent . As I mentioned before, this is seen for all CRAN modules which access X11 graphics (e.g. as R modules cairodevice, gwidgetsrgtk2, tkrplot, etc). -- Ticket URL: <https://trac.macports.org/ticket/46856#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts