Red Hat Bugzilla – Bug 217524
Review Request: libsyncml - SyncML protocol library
Last modified: 2007-11-30 17:11:50 EST
Spec URL: http://www-sop.inria.fr/geometrica/team/Laurent.Rineau/Fedora/libsyncml.spec
SRPM URL: http://www-sop.inria.fr/geometrica/team/Laurent.Rineau/Fedora/libsyncml-0.4.2-1.src.rpm
Libsyncml is a implementation of the SyncML protocol.
Quote from Wikipedia: "SyncML is most commonly thought of as a method to synchronize contact and calendar information between some type of handheld device and a computer (personal, or network-based service), such as between a mobile phone and a personal computer."
Note 1: This library requires wbxml2, which has been unorphaned. See bug #217180.
Note 2: I have not yet managed to build it with mock, because wbxml2 has not been pushed into rawhide. It was build successfully today. See
Note 3: libopensync-plugin-syncml will follow, blocked by bug #217150.
+ package builds in mock (development i386).
+ rpmlint is silent for SRPM and RPMS.
+ source files match upstream.
+ package meets naming and packaging guidelines.
+ specfile is properly named, is cleanly written
+ Spec file is written in American English.
+ Spec file is legible.
+ dist tag is present.
+ build root is correct.
+ license is open source-compatible. License text included in package.
+ %doc is small; no -doc subpackage required.
+ %doc does not affect runtime.
+ BuildRequires are proper.
+ %clean is present.
+ package installed properly.
+ Macro use appears rather consistent.
+ Package contains code, not content.
+ no headers or static libraries.
+ libsyncml-1.0.pc file present.
+ -devel subpackage exists
%post -p /sbin/ldconfig
%postun -p /sbin/ldconfig
+ no .la files.
+ no translations are available
+ Dose owns the directories it creates.
+ no duplicates in %files.
+ file permissions are appropriate.
(In reply to comment #1)
> + package builds in mock (development i386).
Can you explain how you have used mock? wbxml2 packages are not pushed in FE,
yes. I usually do following trick.
Just add newly created rpms in your extras repository. I never got to use online
repository. I always created own mock environment locally as its easy for me to
add new rpms and test other packages dependent on this new rpms.
Imported and build. Build job