exiscan patch for Exim is deprecated and should be replaced with exiscan-acl current version of exiscan-acl: 4.20-06 for Exim 4.20
That'd break the existing configs due to lack of backwards compatability. If you just want an updated exim ebuild with out exiscan-acl, see bug 20613.
I actually want exiscan-acl The new configuration through exim ACLs is much cleaner If the old exiscan must be supported then I suggest making it a choice in the new ebuild, however I believe all features can be migrated to the new acl format. IMHO migrating now is the way to go, the old exiscan is NOT being maintained. Additionally I propose a new USE variable exiscan-acl that would optionally add exiscan-acl to exim. This USE variable would be on by default, but could be turned off by those that want a more stock exim. If the old exiscan is still desired by many, then an exiscan USE variable could also be added. This USE variable would be off by default but could be turned on by those that want to use the old exiscan. The ebuild should provide a warning that exiscan is not being maintained, and that security/stability is at their own risk. The USE variable approach could also be used to support SA-Exim. An alternative Exim patch related to SpamAssassin. I will file another bug report proposing a USE variable sa-exim for the purpose of enabling SA-Exim patch.
Yea, I like exiscan-acl as well, and I very much want to use it. However I don't want an ebuild to clobber my existing config file or break my existing system by not being backwards compatible, either. When I'm ready to switch to exiscan-acl, I'd like to be able to do so at my schedule, rather than have portage tell me when to do it...
exiscan could be default USE variable with a warning about new exiscan-acl USE variable this way no one upgrading exim would inadvertenly switch to exiscan-acl but those that want exiscan-acl can have it
Created attachment 12857 [details] Updated ebuild for Exim 4.20 with exiscan and exiscan-acl USE This should allow for building Exim 4.20 with exiscan or exiscan-acl TODO set a default make the choice exclusive, don't allow both patches to be made
Created attachment 12885 [details] Updated ebuild for exim 4.20 with exiscan and exiscan-acl USE Changed the line for pam integration to follow the convention of other ebuilds
Created attachment 12900 [details] Updated ebuild for exim 4.20 with exiscan and exiscan-acl USE Clean up fix small permissions problems with /etc/exim files (was 744, should be 644) move auth_conf.sub from doc to /etc/exim change /etc/pam.d/pam.d-exim to /etc/pam.d/exim (this is actually in the last one) This should be ready to go Barring problems with this, I will begin to integrate sa-exim per bug 21696
Created attachment 13173 [details] Updated ebuild for exim 4.20 with exiscan and exiscan-acl USE Fixed borked symlinks from previous "clean up" (sorry about that) Added support for lmtp USE per bug 21513 Supplied default value for SYSTEM_ALIASES_FILE per bug 21480
I'm having problems getting the digest for exiscan: # USE="exiscan" GENTOO_MIRRORS="" emerge -b exim Calculating dependencies ...done! >>> emerge (1 of 1) net-mail/exim-4.20 to / >>> md5 ;-) exim-4.20.tar.gz >>> No message digest entry found for archive "exiscan-4.20-26.tar.gz." !!! Most likely a temporary problem. Try 'emerge rsync' again later. !!! If you are certain of the authenticity of the file then you may type !!! the following to generate a new digest: !!! ebuild /usr/portage/category/package/package-version.ebuild digest Did an rsync later, problem not solved. I don't generally like to do this, but I wanted to see what would happen: # ebuild /usr/portage/net-mail/exim/exim-4.20.ebuild digest >>> Generating digest file... >>> Computed message digests. # USE="exiscan" GENTOO_MIRRORS="" emerge -b exim Calculating dependencies ...done! >>> emerge (1 of 1) net-mail/exim-4.20 to / >>> md5 ;-) exim-4.20.tar.gz >>> No message digest entry found for archive "exiscan-4.20-26.tar.gz." !!! Most likely a temporary problem. Try 'emerge rsync' again later. !!! If you are certain of the authenticity of the file then you may type !!! the following to generate a new digest: !!! ebuild /usr/portage/category/package/package-version.ebuild digest Longshot: # ebuild /usr/portage/distfiles/exiscan-4.20-26.tar.gz digest !!! doebuild: /usr/portage/distfiles/exiscan-4.20-26.tar.gz does not appear to be an ebuild file. Didn't think so. exiscan of course isn't it's own ebuild, so I'm unable to calculate digests apparently.
The new digests were not added to CVS so rsyncing won't help until they are, Jack? In the meantime you can calc the digest locally by doing: USE="exiscan exiscan-acl" ebuild /usr/portage/net-mail/exim/exim-4.20.ebuild digest The USE vars that cause the ebuild to download the files to be digested have to be on when the digest command is given
That did it. Thanks for the assistance, much appreciated.
Created attachment 13579 [details] Updated ebuild for exim 4.20 with exiscan and exiscan-acl USE Fixes pid file in build Change logging to use /var/log/exim directory by default syslog can still be enabled in /etc/exim/exim.conf
Created attachment 13728 [details] Updated ebuild for exim 4.20 with exiscan and exiscan-acl USE Provide original exim.conf file along with patched version for exiscan or exiscan-acl
Created attachment 13941 [details] Updated ebuild for exim 4.20 with exiscan and exiscan-acl USE patch /etc/exim/exim.conf for maildir delivery if maildir USE is set
Created attachment 13942 [details, diff] files/exim-maildir-4.20-00.patch patch exim.conf for maildir delivery
committed
