Every now and then when I come back to use my daily driver running #Debian #Linux, I got surprised why #apt still does not provided short-formed commands like #pkg in #FreeBSD and #pkgin in #NetBSD do such as:

# FreeBSD
pkg ins vim # same as pkg install vim
pkg sea vim # same as pkg search vim

# NetBSD
pkgin in vim # same as pkgin install vim
pkgin se vim # same as pkgin search vim

# while in Debian
apt search vim # no apt se/sea
apt install vim # no apt in/ins
#Unix #BSD #FOSS

pkgin 25.10.0 released.

Fixes an issue where changes to the pkgdb outside of pkgin operations (e.g. manually running pkg_add) could affect subsequent upgrades and lose autoremove information.

I'll get this into the SmartOS and macOS trunk builds over the weekend.

#pkgin #pkgsrc

I just installed #NetBSD 10.1 yesterday on my laptop with X sets too. I got #Firefox from #pkgin but it failed to launch with a core dump in a normal #ctwm session. Is this expected? Thanks!
I was just about to complain why #pkgin in #NetBSD about having long commands like install, search and list and no short form like install for #pkg in #FreeBSD and then pkgin without any argument slaps me in the face and say no you can just use in se ls for install search and list
#BSD #RUNBSD #Unix #FOSS

pkgin 25.5.0 released.

Includes some important fixes to SUPERSEDES and CONFLICTS support, and "upgrade" will now update any core package tools first.

Should correctly handle the recent php-X.Y -> phpXY-X.Y renames, and fix some other corner cases.

https://github.com/NetBSDfr/pkgin/blob/master/CHANGES.md#version-2550-2025-05-19

#pkgsrc #pkgin

pkgin/CHANGES.md at master Β· NetBSDfr/pkgin

pkgin's official github repository. Contribute to NetBSDfr/pkgin development by creating an account on GitHub.

GitHub

Next version of pkgin will check for upgrades to any installed packaging tools first.

https://github.com/NetBSDfr/pkgin/commit/e5849d8f52215b36a8f8ed6d80e31c15178cff81

Wishing I'd done this sooner so that upcoming fixes for SUPERSEDES would be automatically handled :( Oh well, hopefully will still prove to be useful in the future (or maybe not!)

#pkgin #pkgsrc

upgrade: Upgrade packaging tools first. Β· NetBSDfr/pkgin@e5849d8

If any important packaging tools are installed and have upgrades available then perform only those first, and then instruct the user to re-run "pkgin upgrade" to upgrade the remaining pac...

GitHub

Does anyone know how install certificates so I can use #pkgin? πŸ™

I kinda like the fact that #NetBSD does very little but sometimes it raises very high the learning curve... πŸ˜΅β€πŸ’«

p.s. I completely forgot how slow was the #RPI 2 😩

@archer72 On #FreeBSD, you'd use #pkg.

#pkg_add is a predecessor of #pkg. #pkgin is a part of #pkgsrc, which you can use on #FreeBSD if you really want to. #NetBSD folks might be able to tell you more about #pkgsrc.

After some investigation, I came to the conclusion that pkgin is the way to go for package installation, searching, etc. on NetBSD. Unfortunately, It's not installed by default. After fetching the latest stable pkgsrc, I built and installed it. #NetBSD #pkgin #pkgsrc

For anyone using my macOS binary package repository, I've switched to building against MacOSX12.3.sdk.

Build results look good, and over 24,000 packages are available for both arm64 and x86_64.

Full details on why I had to change, and how to switch to the new repository, are in my post to pkgsrc-users:

https://mail-index.netbsd.org/pkgsrc-users/2024/04/19/msg039367.html

The 11.3 repository will no longer be updated, but will remain available for anyone unable to upgrade past Big Sur.

Any problems, let me know!

#macos #pkgsrc #pkgin

macOS package repository switched to 12.3 SDK