FreeBSD ports package: need a new tag

[mnsanghvi]

I am working on create a FreeBSD ports package but none of the changes from PR #272 seem to be available with the latest v12_33 tag. A tag would be easier to work with in the ports Makefile rather than with a Git commit hash.

[chrisws]

I've created the tag v12_33_FreeBSD

[mnsanghvi]

Thank you!  That works.   Console builds now work in Free BSD ports.   Now onto figuring out the other builds and packaging.   On Apr 2, 2026, at 02:46, Chris Warren-Smith ***@***.***> wrote:chrisws left a comment (smallbasic/SmallBASIC#282) I've created the tag v12_33_FreeBSD —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[mnsanghvi]

Some questions based on feedback I got on the FreeBSD ports package:

• How difficult would it be to check for system versions of the stb and miniaudio libraries and use those instead of downloading from GitHub?
• Is it just the header files that are used from those libraries? Are the tests also used?
• Is there a reason to prefer the GitHub version over what would be available on the system?
• Is there a target to package the various examples in the samples directory?
• The various documentation targets install-info, install-html, install-pdf did not work for me. Is there a way to generate documentation so that it can be included with the package?

[chrisws]

• How difficult would it be to check for system versions of the stb and miniaudio libraries and use those instead of downloading from GitHub?
  That should be possible. We'd need to make changes to the build system. stb and miniaudio are not required for the console build
• Is it just the header files that are used from those libraries? Are the tests also used?
  It's just the header files. We could just maintain our own copies of these.
• Is there a reason to prefer the GitHub version over what would be available on the system?
  At the time, it seemed easier to maintain them as git submodules.
• Is there a target to package the various examples in the samples directory?
  Possible not, but we could add something
• The various documentation targets install-info, install-html, install-pdf did not work for me. Is there a way to generate documentation so that it can be included with the package?
  git@github.com:smallbasic/smallbasic.github.io.git is the "source of truth" for documentation. we could build something to pull details into a man page if this was required.