Created attachment 177700 [details] sublime3 update file I did update the port on all my machine to have the latest sublime, and I am sending the patch.
Created attachment 177701 [details] Fix the file/sublime.in shm problem
Hi, There's already a PR for the update and 32/64 support: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213399 As for the shm problem you mention a fix but this simply updates the "Makefile" to point to the newer version, also the wrapper script warns the users if shm is not "setup". (I typed this before you added the sublime.in patch) "-L" is correct since "shm" should be a symlink not a directory.
-L doesn't seems to work and in the forum lot of people seems to have the same problem even if they add the link, this is why I replaced -L by -d. I did not see that ports update was summit in October.
(In reply to ericturgeon.bsd from comment #3) Could you point to the link? In any case "/dev/shm" should be a symlink if devfs.conf is used.
The linux_base ports now create a directory /compat/linux/dev/shm. When Linux programs look up /dev/shm they will see that directory and not any /dev/shm link you setup with devfs. So all you need to do is mount a tmpfs on /compat/linux/dev/shm. This is explained in the pkg-message of the linux_base ports which should be displayed on installation, but you can take another look at it using "pkg info -D -x linux_base".
(In reply to Tijl Coosemans from comment #5) I see, that removes the need for the check at all in the wrapper script. Maybe its worth mention in the wiki though? I know I spend sometime figuring out the issue back when I submitted the port which was the main reason for adding a check to the wrapper script. Or accept the "-d" patch. But in any case there's already a PR for the update of the port.
*** This bug has been marked as a duplicate of bug 213399 ***