i cannot understand why, if a feature is known to be broken, it's exported as use flag. why not disabling by default and offer the use flag when it's fixed? now it's just making the ebuild to fail and force used to disable it manually per package rule. * Note: Support for all IM protocols are controlled by use flags. * Make sure you've enabled the flags you want. * * * LDAP support is a work in progress * and does NOT work AT ALL right now. * >>> Unpacking source... >>> Unpacking bitlbee-1.1dev.tar.gz to /mnt/Dati/Gentoo/tmp/portage/net-im/bitlbee-1.1/work >>> Source unpacked. >>> Compiling source in /mnt/Dati/Gentoo/tmp/portage/net-im/bitlbee-1.1/work/bitlbee-1.1dev ... BitlBee configure LDAP support is a work in progress and does NOT work AT ALL right now. * * ERROR: net-im/bitlbee-1.1 failed.
Well, so remove it from your USE flags if you dislike this.
(In reply to comment #1) > Well, so remove it from your USE flags if you dislike this. It's really amazing that you can't manage to reassign a stupid bug like this to it's maintainer...
don't be inpolite! ...howerver i really think that providing a USE flag that will end with a die() on all condition is simply absurd. i continue to think that it's better to disable use flag until we can switch ldap support on/off
(In reply to comment #3) > ...howerver i really think that providing a USE flag that will end with a die() > on all condition is simply absurd. Sigh, there's no die on USE=ldap anywhere in the ebuild...
you're right, it's in the configure ./configure --ldap=1 BitlBee configure LDAP support is a work in progress and does NOT work AT ALL right now. root@blight bitlbee-1.1dev # ./configure --ldap=auto BitlBee configure LDAP support is a work in progress and does NOT work AT ALL right now. root@blight bitlbee-1.1dev # ./configure --ldap=0 BitlBee configure Architecture: Linux Configuration done: Debugging disabled. Binary stripping enabled. Using event handler: glib Using SSL library: gnutls Building with these storage backends: text xml Building with these protocols: msn jabber oscar yahoo same if you don't pass ldap switch. ebuild should remove the ldap switch
...no news...
Fix in cvs