I've successfully emerge'd and am using dspam and wordpress on ~amd64. I'd like to see those unmasked for ~amd64.
I did have one problem with wordpress, I couldn't login to the site admin after creating the initial database tables. The problem seemed to be a patch applied in the ebuild. I commented this line out of wordpress-1.2.ebuild (in src_unpack):
I also noticed in the dspam ebuild that it builds with root:mail as the user to run as. That works, but if/when the dspam.cgi is included in the ebuild it will be impossible to run as you need Apache's suexec. suexec doesn't run anything for UIDs < 1000. I'd recommened that be changed to dspam:dspam.
Steps to Reproduce:
Portage 2.0.50-r9 (gcc34-amd64-2004.1, gcc-3.4.1, glibc-184.108.40.20640619-r0,
System uname: 2.6.7-gentoo-r11 x86_64 15
Gentoo Base System version 1.5.1
CFLAGS="-march=k8 -O2 -pipe"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
USE="amd64 apache2 apm avi berkdb cdr crypt cups encode foomaticdb gdbm gif gpm
imlib jpeg ldap libg++ libwww mikmod motif mpeg mysql ncurses nls nptl oggvorbis
opengl oss pam pdflib perl png procmail python quicktime readline samba sasl sdl
slang spell ssl tcpd truetype xml2 xmms xv zlib"
I've committed a new login patch for wordpress. Please add all feedback about the login patch to bug #53563.
Thanx for the feedback about dspam on ~amd64. But I'll probably won't unmask it for ~amd64 until more conclusive testing by the amd64 herd.
As for your feed back on permissions, I've updated the owner and group to dspam. You might want to do an "emerge dspam" just to check it out.
Lim Swee Tat