Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • I am in fact skipping the whole binary ports part, as there is nothing to build for my package, it’s literally a matter of dropping a bunch of files from the source tree onto the target system. Creating a port, i.e. telling a build system mostly made for building native code from C sources, to copy a few files, seems like massive overkill for this use case. Even with ports I would still need separate binary packages for, say, distributions with only curl available and those with only wget, since pkg does not seem to have a way for a binary package to say “I need either curl or wget”. Commented Apr 20, 2024 at 17:10
  • Overkill?!? Minimal makefile is 8 lines for the basic info and then a plist file which lists your files. See Quick porting and simple example. You do have the option for pre/postinstall scripts. See pkg. The goal is however not clear: Distributions? FreeBSD has fetch in the base system. Commented Apr 20, 2024 at 18:35