On 2017/03/08 19:12, Zé Loff wrote: > - Some packages need W^X (e.g. rJava and V8) to run. If you end up > needing those packages I *think* R needs to be flagged as WX_NEEDED, > since they run "inside" R. Not sure if its worth it to flag R only > because of optional packages, though.
We do that for Python already, purely because of a few modules that most people won't be running (webkit in that case), so it probably makes sense for R too. > - If you install those packages on a user library instead of on the > system-wide library, you'll need to mount /home (or wherever your > library is) as wxallowed. > > - At compile time, some packages run tests with W^X code in them. This > means "configure" will fail, since it detects that binaries can't be > run (for instance it asks if we're cross-compiling). Since packages > are unpacked and compiled in /tmp, this means that at least during > compilation /tmp also needs to be mounted as wxallowed. > > As I told you before, I don't know what the correct approach here would > be, but I believe at least a pkg-readme or a install-message would help. Would it make sense to provide ports for these with things patched so that they work with just the usual requirement that WRKOBJDIR is on a wxallowed filesystem?
