Hi, On Mon, Sep 04, 2006 at 12:52:40PM +0200, Marcel Holtmann wrote: > the 3.5 is coming really soon and fixes another couple of rare race > conditions that can lead to segmentation faults of hcid. The 3.1 version > is not really suited for daily use.
allright, I'm going to wait for bluez 3.5 and then package it. > > > bluez-libs compiled out of the box by just unpacking and moving the > > debian directory over, but bluez-utils needs some work: > > > > * remove bluez-bcm203x package (bcm203x firmware loader removed upstream) > > Not needed at all. You don't wanna support a 2.4 kernel and even if you > really want to, you won't find any of these devices anymore. For all 2.6 > kernels the bcm203x kernel module takes care of loading the firmware. I'm going to drop it after etch release when we'll discontinue support for 2.4 kernels. > > This package has to die and from an USB and udev perspective it was a > really nasty hack. > > > * remove 000_rfcomm_conf_example.patch: the example is already commented > > * remove 004_rfcomm_usage.patch: applied upstream > > Sometimes it is a good idea to feed patches back to upstream so I don't > have to extract them from the packages. yep, I'm used to do it, I must have overlooked these patches. > They are a fully replacement for the ones in the Debian package. That is > another thing that always needs to be discussed with upstream. indeed, this has been discussed extensively in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378839 and on bluez-devel > > To install them --enable-pcmciarules is needed and the correct configure > call. Example is in the README. Otherwise the wrong directory will be > picked for them. okay, thanks. filippo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
