Skip to content

treewide: drop unused packages#28468

Draft
GeorgeSapkin wants to merge 10 commits intoopenwrt:masterfrom
GeorgeSapkin:treewide-drop-unused
Draft

treewide: drop unused packages#28468
GeorgeSapkin wants to merge 10 commits intoopenwrt:masterfrom
GeorgeSapkin:treewide-drop-unused

Conversation

@GeorgeSapkin
Copy link
Copy Markdown
Member

@GeorgeSapkin GeorgeSapkin commented Jan 31, 2026

📦 Package Details

Maintainer:
@changeway
@dangowrt
@inindev
@michyprima
@nbd168
@nicolas-thill
@vidplace7
@yegorich
@zhaojh329
Igor Bezzubchenko?
Toni Uhlig?

Description:

Drop unused packages.

Status:


✅ Formalities

  • I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

Upstream not updated since 2013.

Drop the package since no packages depend on any of the subpackages.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it and it's already in the
archive.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it.

Signed-off-by: George Sapkin <george@sapk.in>
Drop the package since no packages depend on it.

Link: openwrt#26931 (comment)
Signed-off-by: George Sapkin <george@sapk.in>
@michyprima
Copy link
Copy Markdown
Contributor

Hey, sorry was out of the loop. Any specific reason for the drop? I could update the packages I’m the maintainer of next week if it’s okay.

@GeorgeSapkin
Copy link
Copy Markdown
Member Author

@michyprima libopen62541 doesn't seem to be used anywhere, or am I missing something? If so, I don't think it makes sense to keep such libraries in the repo.

@vidplace7
Copy link
Copy Markdown
Contributor

vidplace7 commented Jan 31, 2026

liborcania, libulfius, and libyder are used downstream in Meshtastic OpenWrt Packaging.
I have been working to upstream all needed libraries for a while so that meshtasticd can be submitted, please don't remove these.

@GeorgeSapkin
Copy link
Copy Markdown
Member Author

@vidplace7 what's the plan with the upstreaming?

@vidplace7
Copy link
Copy Markdown
Contributor

vidplace7 commented Jan 31, 2026

@vidplace7 what's the plan with the upstreaming?

I've got a comprehensive post tracking progress here meshtastic/openwrt#2

Unfortunately upstreaming is currently blocked by the ancient protobuf version we currently ship 😢

@yegorich
Copy link
Copy Markdown
Contributor

yegorich commented Feb 1, 2026

We still use both libsoc and libsocketcan in our projects. Please, don't remove them.

@GeorgeSapkin
Copy link
Copy Markdown
Member Author

We still use both libsoc and libsocketcan in our projects. Please, don't remove them.

Which projects? Are they in any of OpenWrt repos?

@michyprima
Copy link
Copy Markdown
Contributor

@GeorgeSapkin it is a dependency of my OPC UA server which was meant to make openwrt easy to interface with existing industrial equipment, and in general libopen62541 is the library you look at if you want to write OPC UA software. I have a working C prototype but never got around to polish it enough to propose it for upstream.

I understand why you want to drop it though

@yegorich
Copy link
Copy Markdown
Contributor

yegorich commented Feb 2, 2026

We still use both libsoc and libsocketcan in our projects. Please, don't remove them.

Which projects? Are they in any of OpenWrt repos?

No, they are not. I mean, my own projects/products.

libsocketcan is a companion library for canutils and iproute2. It gives the programmer means to control a CAN interface programmatically.

libsoc is a helper library for some hw interfaces like GPIO, SPI, etc.

What I want ot say, is that there are users for these libraries and they just don't bitrot here. And if it is possible to leave them there, it would be very welcome.

@BKPepe
Copy link
Copy Markdown
Member

BKPepe commented Apr 7, 2026

I mean, I get both sides. We have a library here with no dependencies, but the projects or products using it aren't upstream. So, it makes sense to me that if someone is actually using the library, they should keep it in their own repository—in other words, downstream. Right now, it's of no use to us, and we can't even verify whether the library actually works and is functional.

If I look at the libsoc library, for example, it's mostly in OpenWrt, openSUSE, and older versions of Ubuntu. So, as far as I'm concerned, it makes sense to remove it, see: https://repology.org/project/libsoc/versions

We already have a ton of packages like this that either aren't actively developed, or there just aren't enough people in the OpenWrt community to keep the individual packages up to date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants