main inclusion report for plasmoid-network-manager

[Jonathan Riddell]

Binary package hint: plasmoid-network-manager

https://wiki.kubuntu.org/MainInclusionReportPlasmoidNetworkManager

[Martin Pitt (pitti)]

This package ships SONAMEd libraries in /usr/lib:

-rw-r--r-- root/root 337736 2009-01-29 14:22 ./usr/lib/libknmstorage.so.4.2.0
-rw-r--r-- root/root 276828 2009-01-29 14:22 ./usr/lib/libknmui.so.4.2.0
-rw-r--r-- root/root 58920 2009-01-29 14:22 ./usr/lib/libknmdbus.so.4.2.0
lrwxrwxrwx root/root 0 2009-01-29 14:22 ./usr/lib/libknmstorage.so.4 -> libknmstorage.so.4.2.0
lrwxrwxrwx root/root 0 2009-01-29 14:22 ./usr/lib/libknmdbus.so.4 -> libknmdbus.so.4.2.0
lrwxrwxrwx root/root 0 2009-01-29 14:22 ./usr/lib/libknmui.so.4 -> libknmui.so.4.2.0

Those need to be split out into a proper libknm4 package, to handle soname transitions correctly. Or, if they are meant to be private libraries, they probably should go into /usr/lib/kde4?

[Jonathan Riddell (jr)]

Those libraries shouldn't be in a public location, upstream are aware of the issue and will move them shortly.

I've moved plasmoid-network-manager to main for now to get it some testing in the next alpha and milestoned this bug so it doesn't get lost.

[Alexander Sack (asac)]

On Tue, Feb 03, 2009 at 11:11:46AM -0000, Martin Pitt wrote:
> ** Changed in: plasmoid-network-manager (Ubuntu)
> Status: Incomplete => Triaged
>

What will happen to the knetworkmanager? It never properly supported
NM 0.7 (kde3) and the kde4 port seems also still far from stable. Will
plasmoid network-mangaer be the only solution in future? Maybe we can
demote knetworkmanger or even remove it then?

Thanks for clarifying.

 - Alexander

[Scott Kitterman (kitterman)]

Package renamed.

[Martin Pitt (pitti)]

Still an issue in the current package. Tentatively assigning to Jonathan, please delegate as appropriate. Milestone blockers need to have an assignee.

[Jonathan Riddell (jr)]

I discussed the private libs issue further with upstream. The general policy in KDE for private shared libs is to not install the headers and to include "private" in the name. In this case the headers aren't installed which I'd consider sufficient to not require a stable ABI policy since no other app can use them. Upstream has agreed to add "private" into the library names but I don't think that's important enough for me to patch in our packages. /usr/lib/kde4 is for dl-loaded plugins only, you can't link against libraries there.