SA 3.1.0 is now in the tree, and additionally I've added -r1 which adds new use flags to support optional software that SA can utilize. I considered just listing these in a post-install message, but the net effect would be the same - the folks on the architectures cc:'d on this bug report still wouldn't be able to use the additional features. I've listed each arch and the package(s) that block the new use flags below. The 3.1.0-r1 ebuild does not currently have you arch available. Most of these packages are perl modules, which should be fairly straigtforward. Please let me know if you have any questions, Mike ~alpha: 'dev-perl/DBD-SQLite', 'dev-perl/Mail-SPF-Query', 'mail-filter/dcc', 'dev-python/pyzor' ~amd64: 'dev-perl/Mail-SPF-Query' ~hppa: 'mail-filter/razor', 'dev-python/pyzor', 'dev-perl/Mail-SPF-Query', 'mail-filter/dcc', 'dev-perl/DBD-SQLite' ~ia64: 'dev-perl/DBD-SQLite', 'dev-perl/Mail-SPF-Query', 'mail-filter/dcc', 'dev-python/pyzor' ~ppc64: 'mail-filter/dcc', 'dev-perl/Mail-SPF-Query', 'mail-filter/razor', 'dev-python/pyzor' ~mips: 'dev-perl/Mail-SPF-Query', 'mail-filter/razor', 'dev-python/pyzor', ' dev-perl/DBD-Pg', 'mail-filter/dcc', 'dev-perl/DBD-SQLite'
Alpha done, thanks Cheers, Ferdy
Ok, marked ~ppc64 including deps
Thanks AMD64. :p Well anyway, I compiled this with and without the many different USE flags available (including the Mail-SPF-Query), and it compiled, installed, started, and stopped just fine. Evolution seemd to grasp it. I can't ensure that the plugins were thouroughly tested but the installation seems to have worked properly. To me, this seems stable enough for an ~amd64 keyword as I've been using it for about 48 hours.
PS. I had to add this to my package.keywords on my AMD64 #=mail-filter/spamassassin-3.1.0-r1 ~amd64 =mail-filter/spamassassin-3.1.0-r1 ~x86 =dev-perl/Mail-SPF-Query-1.997 x86 =dev-perl/Sys-Hostname-Long-1.2 x86 =dev-perl/Archive-Tar-1.26 ~amd64 =dev-perl/Net-CIDR-Lite-0.15 x86
(In reply to comment #4) > PS. I had to add this to my package.keywords on my AMD64 <list of ebuilds> Hopefully those would be keyworded along with sa-3.1 ;)
re-added ~amd64 to -r2
Somehow neither repoman nor emerge (sys-apps/portage-2.1_pre4-r1) complained about this IUSE/DEPEND issue: Index: spamassassin-3.1.0-r2.ebuild =================================================================== RCS file: /var/cvsroot/gentoo-x86/mail-filter/spamassassin/spamassassin-3.1.0-r2.ebuild,v retrieving revision 1.4 diff -u -B -r1.4 spamassassin-3.1.0-r2.ebuild --- spamassassin-3.1.0-r2.ebuild 15 Jan 2006 14:56:22 -0000 1.4 +++ spamassassin-3.1.0-r2.ebuild 6 Feb 2006 17:58:41 -0000 @@ -14,7 +14,7 @@ SLOT="0" #KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~mips" KEYWORDS="~alpha ~ppc ~ppc64 ~sparc ~x86" -IUSE="berkdb qmail ssl doc ldap mysql postgres sqlite spf tools" +IUSE="berkdb qmail ssl doc ldap mysql postgres sqlite spf tools dcc pyzor razor" # To consider (not all may be in tree at this time - mcummings): # dev-perl/Net-SMTP @@ -35,9 +35,7 @@ dev-perl/IO-Socket-SSL dev-libs/openssl ) - berkdb? ( - perl-core/DB_File - ) + berkdb? ( perl-core/DB_File ) ldap? ( dev-perl/perl-ldap ) mysql? ( dev-perl/DBI
I think I'm going to close this bug because in the 4 months that this bug has sat here, another version of SA has been released, and I've finally given up on the archs (so to speak) and finished the keywording that I attempted to start here. Expect another version of this bug shortly.