andersk-auto
commented
10 years ago Imported from trac issue 110. Created by achernya@ATHENA.MIT.EDU on 2013-03-18T21:09:50, last modified: 2013-10-06T21:20:15
Open andersk-auto opened 10 years ago
andersk-auto
commented
10 years ago Imported from trac issue 110. Created by achernya@ATHENA.MIT.EDU on 2013-03-18T21:09:50, last modified: 2013-10-06T21:20:15
Zephyr is currently available in Debian (and as a result, Ubuntu), but not in Fedora or RHEL/EPEL. Packaging this is fairly straightforward, and can mirror the Debian package layout.
Conveniently, this will also allow Fedora to unbundle libzephyr from Pidgin.
I currently have mostly-working packaging that produces (zephyr, libzephyr4, libzephyr4-krb5, zephyr-server, zephyr-server-krb5) packages, and ships with a zhm.service systemd unit. The libzephyr and libzephyr-krb5 packages are co-installable, but the krb5 package will take priority. This is accomplished by dropping an ld.so.conf.d configuration file that is managed by update-alternatives into the packaging. This has the downside that a system with zephyr, libzephyr4-krb5, libzephyr4 and zephyr-server is possible, and likely will not work. I have considered making the libzephyr packages conflict, but this results in a confused yum in some transactions.
Remaining issues to be solved for the packaging: what to do about libzephyr4{,-krb5}-devel packages. Right now, they both provide the same headers, but libzephyr4.so is not directly in /usr/lib{,64}, so -lzephyr does not work out of the box. It has been suggested to use pkg-config to get CFLAGS and LDFLAGS, which could be generated by configure. However, even if we go down that approach, the .pc file would have to be managed by update-alternatives, or would have to go under two separate names; it's not clear to me which is less evil.