NetBSD package

[0323pin]

FYI, I've packaged repofetch for NetBSD and have merged the package into the main repo, https://mail-index.netbsd.org/pkgsrc-changes/2022/10/09/msg261795.html

Regards

[spenserblack]

Thanks for this! I'm not familiar with NetBSD, but from some quick skimming this means that repofetch is now installable with pkgin, right? Would you like to make a PR to update the installation docs?

[0323pin]

Yes, I can make a PR and add it to the README.md.
Yes, you can install it with pkgin depending on which branch you are tracking. On current/development branch it should be available as a pre-compiled binary already tomorrow or the day after. The stable branch is released every three months, so there it should become available soon after Christmas.

I run the bleeding edge branch myself.

[spenserblack]

Hey, just an FYI that I'm considering changing the implementing language. I haven't made any decision yet, but I'm assuming that if I did so it would severely affect the NetBSD package, wouldn't it?

[0323pin]

@spenserblack Thanks for the heads-up. It really depends on what the changes look like. And, it's your app/work so, you decide.

If you move to python, js or, ruby I would ask if someone else is willing to take over as a package maintainer. I don't know anything about packaging stuff on those languages.
My packaging experience is limited to rust, c++, c and go.

[spenserblack]

@allcontributors please add @0323pin for platform

[allcontributors[bot]]

@spenserblack

I've put up a pull request to add @0323pin! 🎉

[0323pin]

@spenserblack Thanks, I'm honoured.

[spenserblack]

@0323pin Just an FYI that I've decided to keep the Rust version in the rust branch, and it may still receive updates.

[spenserblack]

Here's a list of direct dependencies.

Build

Only gem, which is part of the Ruby build tools, should be directly required. gem build to read the .gemspec file and build a .gem file, and gem install to read that .gem file and unpack it to the correct location. gem.mk might be able to offer some more info. Technically, I don't think even gem is required if its behavior is mimicked by manually copying all files.

If docs are going to be built, then yard might be considered a build dependency.

Runtime

• dotenv (this seems to be a deleted pkgsrc package)
• git (Ruby gem)
• actionview (I'd eventually like to drop this dependency, because it feels like overkill for only a couple of utility functions)

Optional (required by plugin)

• ruby-octokit Is optional, but highly recommended. In Rust terms, default-features = ["octokit"]
• faraday-retry is optional, and honestly just added to silence a warning that octokit generates.

[0323pin]

Awesome, thanks!
I wasn't expecting you to dig through pkgsrc to find availability 🤗
Thanks for going the extra mile.

[spenserblack]

Just a heads up: #222 will change sawyer from an indirect dependency (via octokit) to a direct dependency.

[0323pin]

Cheers! I was away for X-mas and didn't have time for creating a new package. I'll have time on Monday, will let you know if I "hit the wall" 😄

[spenserblack]

No problem, enjoy your break!

[0323pin]

@spenserblack Just FYI, I've created a skeleton package update today. Unfortunately, the default ruby version has been bumped to 3.1.3 which would force me to re-build the whole ruby infrastructure locally. I don't have the time or resources needed for this, so I need to wait for pre-compiled binaries to become available from the servers before I can test the build.

I'm a bit concerned with the missing dependencies, ruby-dotenv and ruby-git but, until I can get my hands on fresh ruby binaries, I won't be able to test any builds.

Sorry for the delay :(

[spenserblack]

Sorry for the delay :(

No worries, there's no rush 🙂

Thanks for the head up!

[spenserblack]

Just had a thought: would you know how frequently NetBSD's default Ruby version bumped? I test 3.1 in the CI, but I wonder if it would be worth it to test 3.1.3 explicitly for the NetBSD package.

[0323pin]

Just had a thought: would you know how frequently NetBSD's default Ruby version bumped? I test 3.1 in the CI, but I wonder if it would be worth it to test 3.1.3 explicitly for the NetBSD package.

Honestly, I have no clue how often the default Ruby version is bumped. Usually, I don't keep track of it as I mostly deal with Rust packages.

I've asked our Ruby expert for help and he has managed to get repofetch running. Although, he will need to add a few of the currently unavailable dependencies first. I'll ask nicely if he can update the repofetch package to the newest version.

[spenserblack]

Alright, thanks so much for working to get repofetch available on NetBSD!

[0323pin]

@spenserblack Thanks to Takahiro Kambe, we now have the Ruby version :)
https://pkgsrc.se/sysutils/ruby-repofetch

[spenserblack]

Thank you so much! I appreciate all the hard work!