Version 2004 has been out for a while, and adds IPv6 support. I hacked up a quick ebuild based on uw-imap-2002e-r2.ebuild in portage. It checks the ipv6 use flag in the src_compile section. Reproducible: Always Steps to Reproduce:
Created attachment 35478 [details] ebuild (net-mail/uw-imap-2004.ebuild)
Could you please provide a diff file against the original ebuild? It makes it easier for us to find out what you have changed or added. Thanks.
No problem, I made up a new ebuild using uw-imap-2004e-r4.ebuild as a base. I'll attach the ebuild and the diff.
Created attachment 40907 [details, diff] Diff against uw-imap-2004a.ebuild
Created attachment 40908 [details] New ebuild for uw-imap 2004a (net-mail/uw-imap-2004a.ebuild)
Whoops, I had a brain fart there. The new ebuild is based on uw-imap-2002e-r4, and the diff is against that ebuild.
There is 2004a package on upstream ftp, and after changing the name of your ebuild to uw-imap-2004a.ebuild, it doesn't install cleanly - it wants to copy some man files that don't exist, and I've noticed at least one "broken pipe" message along the build. Could you possibly have a closer look at the ebuild?
Created attachment 41022 [details] Another revision of 2004a ebuild Ok, I just changed the line: doman src/ipopd/ipopd.8c src/imapd/imapd.8c To: doman src/ipopd/ipopd.8 src/imapd/imapd.8 That took care of the man page issue. As for the broken pipe, I assume you're talking about the "yes" command. If you read the yes(1) man page, you'll realize that a broken pipe there doesn't matter and is actually hard to avoid. In fact, the broken pipe occurs in the "stable" uw-imap-2002e-r1.ebuild. Thanks for pointing it out, but I didn't cause that one.
Added to CVS portage, thanks for the ebuild!
