schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
I've switched my macOS arm64 binary package builds over to targeting the 14.5 SDK. This is necessary to continue to support modern software with newer C++ requirements.
If you are still on the 12.3 SDK packages then head over to https://pkgsrc.smartos.org/install-on-macos/ and follow the "ARM 14.5+ (upgrade)" instructions.
If you are new to this, follow the main instructions to install the full bootstrap kit.
Telescope is now available on pkgsrc (below you can see it running on SPARC). With a few patches [1], it builds and runs fine on Solaris too.
Thanks @op@bsd.network, @thomasadam@bsd.network, and others for contributing to this project.
[0] https://telescope-browser.org/
[1] https://github.com/NetBSD/pkgsrc/tree/trunk/net/telescope/patches
#introduction ― I decided to create an alt account here to allow me
to connect more easily with SDF community.
My primary focus will be on tech-related things I like:
#pkgsrc on #netbsd #illumos and #slackware
#unix #sdf #gopher #smolnet #usenet #dos #c #lisp
#selfhosting #homeserver #permacomputing #lowtech
#hamradio #progrock #progmetal #ambient #postrock
#90s #scifi #cyberpunk #novels #seinen #manga
はてなブログに投稿しました
NetBSD/amd64,i386 10.1 ておくれLive Image 20250815版 - tsutsuiの作業記録置き場 https://tsutsui.hatenablog.com/entry/teokure20250815
#はてなブログ #NetBSD #pkgsrc #mikutter
In case anyone else stumbles on this, I got pkgsrc's fetch failing on Void Linux with "SSL support disabled". Had to add the "openssl" option to net/libfetch and "make replace" that and net/fetch. #pkgsrc #VoidLinux
Am giving FUSE-t a spin on my #pkgsrc #macOS build host, allegedly it's a significant improvement over macFUSE (no kext sounds good!).
Unfortunately it clearly isn't.
"FUSE-T offers much better performance and this is due to excellent macOS client side NFSv4 implementation"
I've had many issues with macOS NFS over the years, and it's really no surprise to me that this is just blatantly false.
When you can tell just from watching the speed of ./configure output scrolling you know it's bad.
@justine What’s in my homelab? Hmmm…
The main NAT router / IPv6 router / firewall / DNS / DHCP / stratum 1 time server is a 2014 era AMD Athlon. Way back Fry’s Electronics was selling AM1 motherboards with quad core 2 GHz Athons, heat sinks and fans for something like $45. I bought quite a few. They’re reasonbly fast, tiny (mini-ITX), take very little power, and can take 32 gigs of memory.
My distcc / VM / qemu / NFS / sequence alignment system is a Ryzen 5900X with 64 gigs.
Building #NetBSD #pkgsrc binary packages are:
Then, for m68k packages:
I also have a Sun Fire V245 to compile sparc & sparc64 pkgsrc packages, but that takes more power than the AlphaServer and the Ryzen 5900X combined, so I only run that in the winter.
I'd prefer #NetBSD: https://schmonz.com/2024/06/07/small-arms/
Staged latest shairport-sync for #pkgsrc. Builds on NetBSD, #macOS. Normally I'd commit, wait for evbearmv6hf-el binary package, forget.
Trying something new today: https://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/doc/HOWTO-use-crosscompile
Anyone running my arm64 macOS binary packages from https://pkgsrc.smartos.org/install-on-macos/ on Sonoma 14.5 or newer may want to upgrade to the newer package sets that I've now built:
$ sed -i -e 's/12.3/14.5/' /opt/pkg/etc/pkg_install.conf /opt/pkg/etc/pkgin/repositories.conf
$ pkgin -f update
$ pkgin upgrade
I'll get new bootstrap kits and a proper announcement done soon, but this is all you need to do if you already have the 12.3 packages installed.
The 14.5 SDK is now required by some software.
I was pointing out the poor state of the #pkgsrc doco in #NetBSD a little while ago. This is the area where #FreeBSD is equally bad with #pkgng.
FreeBSD's pkg-create(8) manual page assures us that +MANIFEST files must have "file" entries one per file. But the actual code for the pkg command only looks for a "files" object with an array of files.
Making manifest and "build-info" files for these tools is not a case of doing what the doco says to do.
https://github.com/freebsd/pkg/blob/main/libpkg/pkg_manifest.c#L114
The pace of software is accelerating, and it's no longer possible to produce binary package repositories that are as backwards compatible as they used to be.
I'm shortly going to have to bump my macOS package sets up to a baseline of 14.5, as the current target of 12.3 is no longer sufficient for certain C++20 features like std::ranges::sort which is now required by print/poppler.
First bulk build is in:
https://reports.pkgci.org/Darwin/14.5/arm64/20250724.1420/meta/report.html
I was kinda hoping it'd fix more tbh e.g. numpy.
Nice optimisation now available for anyone using my macOS binary packages from https://pkgsrc.smartos.org
Packages that require fortran support now only depend on the smaller gcc-libs package (7MB) rather than the full gcc package (300MB).
Once you've "pkgin upgrade"ed, remember to "pkgin autoremove" to clean up the now-unused gcc package.
This brings it in line with the SmartOS package sets.
Continuing to push back against bloat one step at a time. Next up, ghc.
@rubenerd I use Radicale and have maintained it in #pkgsrc. I had to write my own authenticator/authorisation to give granular ro/rw ACLs, but it works well with @davx5app and #Thunderbird
Hmm... pkgsrc/lang/gcc14 on NetBSD/i386 9 is broken... I will import a patch from pkgsrc/lang/gcc12... #pkgsrc
I really wish Apple would stop breaking things.
Latest Command Line Tools breaks yacc, m4, etc.
When you accept the installer it prints a completely bogus estimation time.
Then when it finishes, yacc, m4, etc, are still missing and you go around the cycle again.
This really isn't difficult Apple. With a market cap of over 2.5 trillion dollars, I'm pretty sure you can afford to employ a single #pkgsrc developer. They would find these bugs within minutes before release.
Just to give you an idea of how much software GCC 14's default of -Werror=implicit-function-declaration breaks, here are two pkgsrc bulk build results:
GCC 13.3.0: 24835/28450
GCC 14.3.0: 2589/28450
https://reports.pkgci.org/SmartOS/upstream/trunk/20250630.2248/meta/report.html
https://reports.pkgci.org/SmartOS/upstream/trunk/20250701.2248/meta/report.html
I also had to fix up a bunch of things before the build would even start.
This could take a while. And then the fun starts all over again with GCC 15's changes...
@futurebird How about an Amiga 4000 running #NetBSD running nanotodon?
This machine happens to be one of the machines that compiles m68k #pkgsrc binaries for NetBSD.
I love that these machines are still quite useful in 2025, whether running NetBSD or AmigaOS. There was just an update to AmigaOS in March, and I took this machine apart fo install new AmigaOS 3.2.3 ROMs (with Kickstart 47.115).
It’s getting harder and harder to find modern programs for classic Mac OS or even PowerPC Mac OS X, but people are keeping SSL, ssh, usable browsers and email clients, games and all sorts of other things up to date on Amigas.
It finally finished in just under 66 hours.
And now to do it all over again because lang/rust got changed during a freeze.