baserev update by copy to link target

• Files Changed
• Browse Source

- Changed file luajit2-name.patch and fixed package.path for modules.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Removed %check (tests don't run, and it's not known how to run them).

• Files Changed
• Browse Source

initialized devel package after accepting 1171749

• Files Changed
• Browse Source

Trying again. :-)

I think I figured out what confusion in the title you were referring to.
In luajit2 from OpenResty only the project directory and another internal version are renamed.
But everything else, library name, executable name, directory with header files, pc-file and even man-file remained unchanged.
This is what is really confusing and makes lualit2 incompatible with luajit.

I fixed this in the patch luajit2-name.patch and now luajit2 is not dependent on or related to luajit in any way, except for the html documentation, it has its own executable, library and header file directory names.
Also pc and man files have been corrected.
Now it does not conflict with luajit and can be installed simultaneously with luajit without interfering with it.
By accident something intended to be built with luajit can NOT be built with luajit2!

As for the openresty package, I strongly recommend to remove it after adopting luajit2, as nobody needs it as it is!

About the tests, upstream didn't document how to use them correctly, so I decided to check with them, I hope I guessed correctly.

https://github.com/openresty/luajit2/issues/226

Leap has a too old version of perl and they can only work in Tumbleweed.

If you have any constructive comments, I'm willing to discuss them. :-)

• Browse Source