On Sat, 25.10.08 17:37, Lennart Poettering (lennart at poettering.net) wrote: > neither libpulsecore nor libpulsecommon have that -- they change API > every single release. Now libpulse needs to use functions from > libpulsecommon and the other way round. After some discussions with a > few people (such as Diego) I decided it is probably OK to have this > cyclic dependancy on most systems. The dep from libpulse to > libpulsecore is explicit. The dep the otherwise round is not -- which > is fine because programs will link against libpulse and > libpulsecore -- but not exclusively against libpulsecommon. Since > libpulsecore also pulls in libpulse it is hence guaranteed that all > symbols can be resolved. Sorry this is bogus. I wanted to say that the dep from libpulse to libpulse*common* is expcilit. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4
