[Bug 166547] Review Request: multisync - Calendar (and other PIM data) synchronization program
bugzilla at redhat.com
bugzilla at redhat.com
Fri Aug 26 19:33:57 UTC 2005
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: multisync - Calendar (and other PIM data) synchronization program
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=166547
------- Additional Comments From bugs.michael at gmx.net 2005-08-26 15:33 EST -------
> %post -p /sbin/ldconfig
>
> %postun -p /sbin/ldconfig
doesn't do anything useful when the package only contains plugin DSOs
in %_libdir/multisync/
> %{_datadir}/multisync/pixmaps/
is unowned. You could include it and its contents recursively.
> %package devel
> Summary: Files needed for software development with %{name}
> Group: Development/Libraries
> Requires: %{name} = %{version}-%{release}
> Requires: openobex-devel
> Requires: bluez-libs-devel
> Requires: evolution-devel
> Requires: evolution-data-server-devel
> Requires: wbxml2-devel
> Requires: curl-devel
> Requires: expat-devel
> Requires: openldap-devel
> Requires: pilot-link-devel
It does not become clear at all, why all these requirements?
The multisync API header wants gtk2-devel, glib2-devel [and glibc-devel].
> #ldap
> %{_libdir}/multisync/libldap_plugin.so.*
>
> #evolution (we only have so for this one)
> %{_libdir}/multisync/libevolution2_sync.so
This is the major thing that needs a review or a comment in the spec.
All these DSOs are used as plugins. Does the multisync engine really
load the versioned ones at run-time? Or does it prefer the non-versioned
*.so ones? And in case it loads the versioned ones, and since these
are plugins, there is not much point in shipping the *.so files in the
-devel package. Particularly not, because the DSOs don't live in dynamic
linker's default search path. On the contrary, some packagers like to
include "everything that's there", because some unknown corner-case program
might (!) want to link against a plugin like it's a library (oh well...)
even if it needed an rpath for that.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the fedora-extras-list
mailing list