[MacPorts] #69763: Port sniprun might be lacking something

MacPorts noreply at macports.org
Wed Apr 17 11:39:53 UTC 2024


#69763: Port sniprun might be lacking something
---------------------+---------------------
 Reporter:  Gandoon  |      Owner:  (none)
     Type:  defect   |     Status:  new
 Priority:  Normal   |  Milestone:
Component:  ports    |    Version:  2.9.3
 Keywords:           |       Port:  sniprun
---------------------+---------------------
 I came across `sniprun` a little while back and was keen on trying it out
 and was happy to see that MacPorts seemingly had a port of it.

 However, it seems to be either incomplete, lacking a dependency, or at
 least a full description of where to find the missing links.

 Following the general instructions and adding a `require` to my `init.lua`
 according to the notes etc. I still seem to be lacking a few things that
 seems to be reasonable to expect the port to provide:

 {{{
 E5113: Error while calling lua chunk:
 /Users/myuser/.config/nvim/init.lua:4: module 'sniprun' not found:
         no field package.preload['sniprun']
 cache_loader: module sniprun not found
 cache_loader_lib: module sniprun not found
         no file './sniprun.lua'
         no file '/opt/local/share/luajit-2.1/sniprun.lua'
         no file '/opt/local/share/lua/5.1/sniprun.lua'
         no file '/opt/local/share/lua/5.1/sniprun/init.lua'
         no file './sniprun.so'
         no file '/opt/local/lib/lua/5.1/sniprun.so'
         no file '/opt/local/lib/lua/5.1/loadall.so'
 }}}

 Neither of the `*.so`s are installed by MacPorts, and the `*.lua` files
 are also absent. It could be that the latter are intended to be the local
 configuration, but if the end user is expected to provide them personally,
 `/opt/local/share` seems like an odd location to put them in though.

 The only thing provided by the port is the executable:
 {{{
 $ port -v contents sniprun
 Port sniprun contains:
   /opt/local/sbin/sniprun
 }}}
 And that is confirmed by building the port with `-k`, none of those files
 ends up being produced anywhere in the `work` directory.

 So, my conclusion is that either this port is at least partially broken, I
 missed an unforced dependency, or I am just incredibly stupid. (Actually,
 it may be a little bit of all three, but at this time I am unsure.)

 If anyone knows, please let me know if I missed something here.

-- 
Ticket URL: <https://trac.macports.org/ticket/69763>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list