As a long time OpenWrt user I'd say this is probably a change for the better, but I never had any real problems with opkg.
this post was submitted on 17 Nov 2024
108 points (100.0% liked)
Linux
5268 readers
472 users here now
A community for everything relating to the linux operating system
Also check out !linux_memes@programming.dev
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 1 year ago
MODERATORS
So it's a lot like apt, but with a huge name conflict.
I had never heard of opkg. I looked it up:
opkg: Fork of ipkg lightweight package management intended for use on embedded Linux devices;
ipkg: A dpkg-inspired, very lightweight system targeted at storage-constrained Linux systems such as embedded devices and handheld computers. Used on HP's webOS;
Wikipedia has no dedicated pages for either of them. I guess they're quite niche.
I've never seen it used outside of OpwnWRT. I assumed they made it specifically for it.
They version hasn't changed since 2011 if that tells you something.
Opkg is available for buildroot and some other embedded frameworks
Hopefully it can actually preserve packages across updates which is incredibly annoying to have to handle manually.
EDIT: Just found about this attended sysupgrade package which should help until when/if the new package manager fixes the issue.
The underlying tool is getting replaced in 23. The new tool requests the new image with the packages from the build server.
It was about time, opkg is the worst package manager ever.
Great if true
He says it was unexpected but it's been being talked about on the GitHub for quite some time now. It was really just a matter of when they decided to do it.
It is a hard switch