Because the port (and by extension its package) is properly registered as being "installed" and can therefor be easily updated or removed. You will also have no problems with dependencies, or ports that depend on this particular port. In short, it makes everything easier to manage.
That's also a good reason, in general, to use the FreeBSD port/package instead of downloading original sources and building everything yourself. Lots of ports require patches, some more than others, to build and work correctly on FreeBSD. The port submitter/maintainer already figured all this out, so you can simply do
pkg install something or cd /usr/ports/example/something && make install and it'll work.lang/go124 does have a maintainer (go@freebsd.org, this info was gleaned from the Makefile for lang/go-devel.). If you look at the instructions for source-based installation, they are centered on processor architecture rather than specific OS/distro. FreeBSD most likely uses the instructions that are applicable to the
amd64 arch / instruction set.-quarterly and -latest package repos. The -quarterly stuff gets built on a schedule. But even with that, it takes being willing to spend some time doing research and figuring out when your favorite port is going to have a package. Some people find it a fun rabbit hole to go down.In all honesty, if the stuff is in the FreeBSD ports tree, there's no real reason to wait for packages. Just grab the port from the cgit, put it into your own local copy, and you're good to type
make && make install. Do pay attention to versions, though: you keep typing 1.4.2, while even upstream's version is 1.24.2, and the ports tree shows 1.24.2... On your new installation, did you enable the SSHd daemon? if not, the easy way to do that is through
bsdconfig. Just dig around the menus, the option to turn it on is definitely there.Indeed, typing is not one my talents.
No, I'm wanting to carry on developing my Go/GStreamer application, but on better hardware and away from Linux. I'm attracted to FreeBSD's stability, when compared with Linux.
I'm using go-gst bindings which is actively supported. It has some known bugs, but what hasn't?
Yes. I can ssh from my Mac into FreeBSD. VSCode doesn't support BSD. Some have work-arounds, but Microsoft keeps moving the goal post. This is probably the biggest problem for me and may force me to return to Linux - or spend months learning and configuring vim.
If you want to develp your own Go/GStreamer application, for your own use, that's nice, but you still have to decide on which OS you want to run it when everything is said and done. Because that's where you will need to do your development, as well.
I'd prefer to get completely away from Microsoft. That's why my main machine is a Mac, but I'm short on desk space so I use VScode to access the target machine. IE. I would like the target machine to be a headless mini-pc running FreeBSD or Linux. The app will be open source for the amateur television community.
I have read this. Too complicated and likely to break with every MS update.
In which case, I think your best bet is to install devel/py-jupyter-server on that headless FreeBSD installation, and learn a bit about Jupyter Notebooks, how they work, and what are the benefits and pitfalls of using them.
Is that how you discovered FreeBSD, by using it without knowing?
Having owned a Commodore PET, Northstar Horizon, and a few Intel builds running anything I could get my hands on, including SVR4 and SCO, my first Apple product was the Macintosh LC.
I only need a headless server for this application. The purpose of which is to control a microwave DATV repeater, situated at some remote location. Basically, RF in -> demodulate -> decode -> switching -> encode - modulate -> RF out. The switching part is there to insert a slideshow when no RF is being received. The RF parts are external to the mini-pc and there are multiple RF and Ethernet inputs and outputs.
gstreamer.freedesktop.org
What you say is correct, but I like the extra features an IDE provides, although I'd prefer one not owned by Microsoft.
