Here is a modified ebuild + some patches to support pam and ldap Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: hylafax 4.1.xx doesn't have pam and ldap support Portage 2.0.50-r9 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r1, 2.6.7-uml1) ================================================================= System uname: 2.6.7-uml1 i686 AMD Athlon(TM) XP 2500+ Gentoo Base System version 1.4.16 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer " CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/alias /var/qmail/control /var/spool/fax/etc" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer " DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs buildpkg ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://10.0.4.11/gentoo-portage" USE="X aalib acl apache2 apm arts avi berkdb cdr crypt cups dvd encode esd fbcon foomaticdb gdbm gif gnome gpm gtk gtk2 imap imlib java jpeg kde kerberos ldap libg++ libwww lzw mad mikmod mmx motif mozilla mpeg mysql ncurses nls oggvorbis opendlm opengl oss pam pdflib perl png postgres ppds python qmail qt quicktime readline sdl slang spell sse ssl svga tcltk tcpd tetex tiff tinydyndns truetype vhosts virus-scan x86 xml xml2 xmms xv zlib"
Created attachment 38110 [details, diff] improved ebuild
Created attachment 38111 [details, diff] ldap patch
Created attachment 38112 [details, diff] ldap patch part #2
Created attachment 38113 [details, diff] pam patch part #1
your patches are pretty big. did you tried to send them upstream first? I'd feel much more comfortable if these babies are accepted by the upstream, otherwise maintenance would be a hell!
these are already integrated in the 4.2.x version
So all I need to do is add ldap & pam flags to IUSE, right?
Yes ...it's all "explained" in the diffs. Essentially, I've backported two functionalities from the 4.2.x brach.
I don't see anywhere in the last version (4.2.0) sources, anything about ldap. Is it a feature backported from CVS?
You can find pam support in the 4.2.0 release. Some months ago, the same author of the pam patch, Marcin Giedz, published the ldap patch on the hylafax-user mailing. It will be probabily integrated in the next release. IMHO the ldap patch is not so intrusive and many users can benefit from it. From my point of view it's unuseful to have an enterprise class fax server without a good authentication mechanism (like ldap).
In other words, pam is absolutely necessary, ldap is "optional" (alias we can also use it with pam_ldap and nss_ldap).
Support for pam is already included in 4.2.0, so I will close this bug. Maybe future versions will have direct ldap support.
