sile 0.10.3

[alerque]

• Have you followed the guidelines for contributing?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

---

[alerque]

See upstream release checklist and issue about git HEAD builds needing history.

[alerque]

@simoncozens I attempted a fix here for the Lua path issue. I think the wrapper script should now just prepend its own paths instead of completely clobbering what Lua would otherwise have had. I am completely unable to test this though so I'm leaving the PR in draft mode for now until there is some confirmation that it works.

[alerque]

If this works, another thing to try and simplify (and avoid the Lua invocations) is this:

diff --git a/Formula/sile.rb b/Formula/sile.rb
index 3909af5e6b..90501c13ce 100644
--- a/Formula/sile.rb
+++ b/Formula/sile.rb
@@ -139,8 +139,8 @@ class Sile < Formula
     (libexec/"bin").install bin/"sile"
     (bin/"sile").write <<~EOS
       #!/bin/bash
-      export LUA_PATH="#{ENV["LUA_PATH"]};$(lua -e 'print(package.path)')"
-      export LUA_CPATH="#{ENV["LUA_CPATH"]};$(lua -e 'print(package.cpath)')"
+      export LUA_PATH="#{ENV["LUA_PATH"]};;"
+      export LUA_CPATH="#{ENV["LUA_CPATH"]};;"
       "#{libexec}/bin/sile" "$@"
     EOS
   end

The double ;; should be a shortcut to tell Lua to add it's default paths, but I was unsure if that worked from the environment variable or only internally after it was already running.

[simoncozens]

PR as written works fine. Checking the suggested patch now.

[simoncozens]

Double-semicolon solution also seems to work.

[alerque]

@simoncozens Thanks. The double-semicolon trick is less process overhead so we'll go with that.

[SMillerDev]

Looks good, can you squash your commits?

[alerque]

@SMillerDev Done.

[alerque]

It seems like CI got stuck, it has been "pending" for a day. I'm rebasing on master just to poke it (since I don't have any other way of triggering it to retry).

[alerque]

Hey looks like that worked. If there is a different way to un-jam CI checks that never return I'd be happy to learn.

[SMillerDev]

You can ask brewtestbot to test this please

[chenrui333]

Thanks @alerque!!