#pkgsrc

7 posts · Last used 6d

Mid September #NetBSD #pkgsrc 2026Q2 binary package count update: 11.0: aarch64eb 26342 (+326) 11.0: alpha 11278 (stopped) 11.0: earmv4 8569 (+1939) 11.0: m68k 18739 (+1793) 11.0: powerpc 24272 (+1393) 11.0: riscv64 21612 (+108) 11.0: sh3el 10417 (+378) 11.0: sparc64 5147 (+2573) 11.0: vax 7646 (+148)
1
1
0
0
Looks like, with the great help of @AnachronistJohn@zia.io , @abs0@mastodon.sdf.org and @jaypatelani@bsd.network , I switched my NetBSD system from using binary packages via pkgin to the pkgsrc and building packages from source :drgn_aww: https://eugene-andrienko.com/2026-09-07-bsd-pkgsrc-ports.html For now, it works and I'm able to have some packages in my system, with the necessary compile-time options. And only one version of Python interpreter installed, not two :drgn_blush_giggle:. Also removed a lot of unnecessary packages, so the disk space usage went down from 18 Gb to 17 Gb :drgn_blush_giggle: #NetBSD #pkgsrc
21
1
15
0
Decided to dig into what I initially suspected was hardware issues on a host performing "pkgin upgrade" very slowly. No, turns out it's legitimate requests hammering the disks, with pkg_delete performing an MD5 check on every file it is about to forcibly remove anyway. Eventually it'd be nice to add a flag for this, but for now I've removed it for my builds: https://github.com/TritonDataCenter/pkgsrc/commit/87055e3a0c53f409a0cf1efa887a3cb96afe0757 This will be in macOS and SmartOS builds soon, and will significantly improve upgrade performance. #pkgsrc
5
1
5
0

portability(TM) #netbsd #pkgsrc #tigersrc

  • alix3d3 (i586) - it finds out what uses SSE2 when it shouldn't
  • er4 (evbmips64n64eb) - it finds out when things hardcode a list of supported archs
  • mac mini (powerpc; usually runs darwin) - it finds out when things don't specify a c/c++ lang std
  • olimex a64 (aarch64) - it finds out when the arm drivers get too piney.
  • banana pi (earmv7hfeb) - ugh.
  • blade 150 (sparc64, bottom) - it finds out EVERYTHING.

100% not running 24/7.

56
7
22
0
If you've ever built a non-trivial amount of software on Solaris / illumos you've almost certainly hit math function errors like this: error: call of overloaded 'log(int)' is ambiguous I got fed up of adding patches to pkgsrc, and I believe I have a patch that fixes this once and for all. https://www.illumos.org/issues/15209#note-4 I'd appreciate wider testing. I've already tested it in a full ~28,000 package bulk build, but changes like this terrify me, and you can't be too careful. #solaris #illumos #pkgsrc
7
8
4
0
You've seen all posts