On Tue, 06.10.09 09:19, Patrick Shirkey (pshirkey at boosthardware.com) wrote: > I can't tell if you are referring to only users here or if you are > saying it is not easy for anyone including developers? Either way > the situation could be improved for genuinely interested developers > by providing the complete build instructions which are currently > missing from the docs online and in the package. Generally I believe building PA is only interesting for three types of developers: those who want to hack on PA itself, distribution developers who want to integrate it into a distribution and developers that do low-level hacking on system software directly related to PA. If you compile PA yourself because you want to hack on it, then I strongly reocmmend simply running it from the build tree, and not installing it. That's how I do things. Since a few releases back we actually detect whether we are run from a build tree and not installed and if that is the case we fix up the search directories up in a way so that everything points to the build tree, not the installed version. That means that buildin+running PA from the build-tree requires nothing more than typing "./bootstraph.sh && make -j6 && ./pulseaudio". Integrating PA into your distribution is hard. It interfaces with so many other packages. If you do integration like this then you are expected to know your way around very well. And everything that is not obvious I nowadays post on the pa ml with a [PACKAGERS] subject prefix or I ping the maintainers i know on irc. If you do low-level hacking on software directly related to PA then you should probably install a development distro such as Rawhide, where you get the newest stuff for free. In the first two cases cases it is expected that you read the output configure.ac and install what is missing, as it is for every project. This should not need further comments, should it? Also, the deps list you find in the wiki, too. If you are a user then you should use tha PA version that is shipped with your distro. If you want a newer version, then upgrade your distro. If you are a developer who writes third party apps then you should stick to a released distro, too. But of course you should really make sure to run the latest one. > On my F11 I have libsndfile-1.20 installed manually with > > ./configure --libdir=/usr/lib64; make; make install I can only advise not to try this. /usr/lib64 is the domain of the package manager. You shouldn't fiddle with that. Only the package manager should. For you there is /usr/local. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4
