Bug 269858 - knotify in kdebase-runtime installs headers (against policy)
Summary: knotify in kdebase-runtime installs headers (against policy)
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: knotify (show other bugs)
Version: 4.6
Platform: Fink Packages macOS
: NOR normal
Target Milestone: ---
Assignee: Olivier Goffart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-01 02:23 UTC by Benjamin Reed
Modified: 2024-05-04 19:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Reed 2011-04-01 02:23:29 UTC
Version:           4.6 (using KDE 4.6.1) 
OS:                OS X

the knotifyplugin library in kdebase-runtime has 2 issues which are making it problematic to package:

1. kdebase-runtime is supposed to contain no libraries other than private ones, and should install no headers
2. the knotifyplugin library is built without a version number, which gives it the name "knotifyplugin.dylib" on OSX, with a "current_version" of 0.0.0.  0-versioned libraries on OSX are special cases and not treated like properly-versioned libraries when it comes to complaining about ABI and compatibility issues.

knotifyplugin should, I presume, move to kdelibs, where other public libraries with headers go.  Additionally, as a public library, I would assume it should get the default versioning, like other libraries in kdelibs:


kde4_add_library( knotifyplugin SHARED ${knotifyplugin_SRCS})
+
+ set_target_properties( knotifyplugin PROPERTIES VERSION ${GENERIC_LIB_VERSION} SOVERSION ${GENERIC_LIB_SOVERSION})


Reproducible: Always

Steps to Reproduce:
compile kdebase-runtime 4.6.1

Actual Results:  
unversioned library is built, and headers are installed

Expected Results:  
kdebase-runtime should contain only runtime plugins, binaries, and private libraries (and supporting files)
Comment 1 Jeffery MacEachern 2011-04-01 05:20:38 UTC
My apologies, I didn't take care of that properly. I'm currently coming up on exams, so I won't be able to fix it for the moment.
Comment 2 Christoph Cullmann 2024-05-04 19:11:05 UTC
I think that is fixed in frameworks.