Hi all, I have built RPMs for libsynce, librapi2, and odccm that seem to work, but I have a few questions before making them official:
- The archive names that are available for download unpack to different folder names (synce-libsynce-0.10.0.tar.gz extracts to libsynce-0.10.0). The RPM builder assumes that they match, and so I have to rename the archive to match the unpacked name. Could these be aligned? I wasn't sure which name was the "preferred" name. This doesn't affect the viability of the resulting RPMs, just their names. - I can't launch odccm out of the box because odccm.conf is not being installed. I wasn't sure if the location of this file is a distro-specific thing. On my Fedora Core 6 machine, it needs to be placed in /etc/dbus-1/system.d. I could have the RPM install there by default, but if this non-standard it's probably not worth it. How is this handled in the Debian packages? - It looks like libsynce installs into /usr/local/lib, which is not in the default library path on Fedora. Is this the expected result? It looks like librapi2 installs into /usr/lib, and so there isn't an issue there. If I install the three RPMs on a clean machine, I have verified that with the correct USB driver and the odccm.conf file in place, I can list the device contents with pls, which was my simple smoke test. I will start taking a crack at RPMs for the sync-engine in the meantime. -- Eli ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
