treewide: drop unused packages#28468
Conversation
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>
|
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. |
|
@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. |
|
liborcania, libulfius, and libyder are used downstream in Meshtastic OpenWrt Packaging. |
|
@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 😢 |
654dd28 to
f48104b
Compare
|
We still use both |
Which projects? Are they in any of OpenWrt repos? |
|
@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 |
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. |
|
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 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. |
📦 Package Details
Maintainer:
@changeway
@dangowrt
@inindev
@michyprima
@nbd168
@nicolas-thill
@vidplace7
@yegorich
@zhaojh329
Igor Bezzubchenko?
Toni Uhlig?
Description:
Drop unused packages.
Status:
liborcaniaused in future Meshtastic packages: treewide: drop unused packages #28468 (comment)libyderused in future Meshtastic packages: treewide: drop unused packages #28468 (comment)libulfiusused in future Meshtastic packages: treewide: drop unused packages #28468 (comment)✅ Formalities