Project update

[maxirmx]

Hi @bradgessler

Here is the working sample. It creates an artefact that can be downloaded and executed

1. To use boost on GHE we have to run

brew update
brew bundle -f

it is not something specific to tebako, they have macOS runners in an unstable state. Most likely this issue is not permanent.

2. You are not required to run bundle before tebako press

Furthermore if you run brew bundle then Gemfile.lock will indirectly contain for reference to Ruby version
For example, your Gemfile.lock referenced Ruby 3.3.3 that we do not support
There is an issue that we will address in the next release, somewhere in January. For now please do not bundle or remove Gemfile.lock before packaging

Thanks

[bradgessler]

Thanks for looking at this! It's probably best if I pull the Ruby version out of the Gemfile.

I think I figured out a way to build & package Ruby apps with bash and no packaging, which I talked about at https://bsky.app/profile/bradgessler.com/post/3ldmiwxc26k24. I'm going to shift into putting more of my resources behind that and less time trying to get it working with Tebako. That said, I'm happy to keep these issues open and work through them if you want to keep working on them, but I'm also happy to close all the issues I opened to keep the project issue tracker clean.

[maxirmx]

Sure, if you have development environment installed at the target system you do not need tebako or travelling rubt or any other packager.
The issue comes when you do not have development environment installed. You can also have dependency on Gem with native extension that depends on some local library and it will create additional requirements for the target system.

So ruby packagers are not about easy installation whether it is 41 line or more or less. They are about "not-installation"

[bradgessler]

If I understand what you're saying, there's a lot of dependencies that need to be built beyond Ruby so that it can run on workstations that don't have developer dependencies installed.

An example of that on macOS would be running on a machine without Xcode tools installed (and that whole dev tool-chain) and on Linux, an equivalent configuration.

[maxirmx]

The tools you mention in your blog (ruby-install, ruby-build) are build tools. They do not install binaries they build the binaries at the client system. So, the issue is not 'beyonf Ruby'.

You assume that there is dev tool-chain at the target system. If so you do not need a packager.
Well, you do not need a packager until you face complex gem or native library dependency.

How do I know I need tebako