net-mail/courier-imap-4.1.3 released!
Hi! Oke, i tested it. Renaming ebuild works fine! All previous patches works fine! compiles & works!
Portage 2.1.2.9 (default-linux/x86/2007.0/server, gcc-4.1.2, glibc-2.5-r3, 2.6.21-gentoo-r3 i586) ================================================================= System uname: 2.6.21-gentoo-r3 i586 Geode(TM) Integrated Processor by AMD PCS Gentoo Base System release 1.12.10 Timestamp of tree: Sun, 01 Jul 2007 21:30:01 +0000 ccache version 2.4 [enabled] dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r7 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.61 sys-devel/automake: 1.4_p6, 1.7.9-r1, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i586-pc-linux-gnu" CFLAGS="-march=k6-3 -O3 -mmmx -m3dnow -fno-align-jumps -fno-align-functions -fno-align-labels -fno-align-loops -pipe -fomit-frame-pointer -mfpmath=387" CHOST="i586-pc-linux-gnu" CONFIG_PROTECT="/etc /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo" CXXFLAGS="-march=k6-3 -O3 -mmmx -m3dnow -fno-align-jumps -fno-align-functions -fno-align-labels -fno-align-loops -pipe -fomit-frame-pointer -mfpmath=387 -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="" FEATURES="ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.gentoo.mesh-solutions.com/gentoo/" LANG="de_DE.utf8" LC_ALL="de_DE.utf8" LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--sort-common -s -Wl,-z,now" LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_COMPRESS="gzip" PORTAGE_COMPRESS_FLAGS="-f9" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apache2 berkdb bzip2 cgi clamav cli crypt ftp gd iconv javascript jpeg jpeg2k mailwrapper mbox memlimit mysql mysqli ncurses nls nptl pam pcre png readline samba sasl session sharedmem simplexml slang snmp sockets spell ssl symlink tcpd threads tiff tokenizer truetype unicode usb vhosts vim-syntax x86 xinetd xml zlib" ALSA_CARDS="none" ELIBC="glibc" INPUT_DEVICES="none" KERNEL="linux" LCD_DEVICES="none" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="none" Unset: CTARGET, INSTALL_MASK, PORTAGE_RSYNC_EXTRA_OPTS
I can confirm that renaming the ebuild and making a copy of courier-imap-4.1.2-as-needed.patch to courier-imap-4.1.3-as-needed.patch works without problems (so far).
*push*
The same trick can be done with version 4.2.0 as well.
(In reply to comment #5) > The same trick can be done with version 4.2.0 as well. > And 4.2.1
(In reply to comment #6) > (In reply to comment #5) > > The same trick can be done with version 4.2.0 as well. > > > And 4.2.1 > And 4.3.0 4.3.0 offers GnuTLS support. If some one prefers GnuTLS ofer OpenSSL then slight changes to the ebuild are needed: @@ -9,14 +9,15 @@ DESCRIPTION="An IMAP daemon designed specifically for maildirs." HOMEPAGE="http://www.courier-mta.org/" SRC_URI="mirror://sourceforge/courier/${P}.tar.bz2" -LICENSE="GPL-2" +LICENSE="GPL-3" SLOT="0" -IUSE="berkdb debug fam gdbm ipv6 nls selinux" +IUSE="berkdb debug fam gdbm gnutls ipv6 nls selinux" # userpriv breaks linking against vpopmail RESTRICT="userpriv" -RDEPEND=">=dev-libs/openssl-0.9.6 +RDEPEND="gnutls? ( net-libs/gnutls ) + !gnutls? ( >=dev-libs/openssl-0.9.6 ) >=net-libs/courier-authlib-0.57 >=net-mail/mailbase-0.00-r8 berkdb? ( sys-libs/db ) @@ -151,6 +152,7 @@ --with-mailgroup=mail \ $(use_with fam) \ $(use_with ipv6) \ + $(use_with gnutls) \ ${myconf} || die "econf failed" # Change the pem file location.
Please, please, please!!! This hasn't been updated in a LONG time, and from what I've heard, there's nothing special that needs to be done...
(In reply to comment #8) > Please, please, please!!! This hasn't been updated in a LONG time, and from > what I've heard, there's nothing special that needs to be done... > Calm down. You still have the possibility to create/use your own overlay. Why all the rush? If you are so certain that things are so ultra easy, then apply for a developer position at Gentoo and try to become the maintainer for net-mail/courier-imap // Steve
Hi Steve, Sorry, but I really don't like complicating things. I am NOT a programmer... far from it. I am fully capable of installing and maintaining a gentoo system, but I do have a paid consultant I work with when I absolutely have something that I cannot do myself... That said - updating packages that are in portage is [relatively] easy - setting up a local overlay is not something I am prepared to do at the moment. I've read about it, and see the potential benefit - but it adds a level of complexity I'm not prepared to accept now. I asked on the gentoo forums about the 'gentoo way' for asking for rev bumps, and who I should be attempting to bribe to get something like this done - they said to file a bug report. I came here, searched, found an existing bug, and simply posted a 'me too!' comment. Maybe you misunderstood my 'Please, please, please!!!' ... I wasn't insisting/demanding, I was begging... so, your snipe about 'becoming a developer was, I think, a bit uncalled for.
(In reply to comment #10) > Hi Steve, > > Sorry, but I really don't like complicating things. I am NOT a programmer... > far from it. I am fully capable of installing and maintaining a gentoo system, > but I do have a paid consultant I work with when I absolutely have something > that I cannot do myself... > > That said - updating packages that are in portage is [relatively] easy - > setting up a local overlay is not something I am prepared to do at the moment. > I've read about it, and see the potential benefit - but it adds a level of > complexity I'm not prepared to accept now. > It is not so complex. Just some small work and responsibility. That's all :) > I asked on the gentoo forums about the 'gentoo way' for asking for rev bumps, > and who I should be attempting to bribe to get something like this done - they > said to file a bug report. > Yes. That's right. Bug report is the way to go. > I came here, searched, found an existing bug, and simply posted a 'me too!' > comment. > > Maybe you misunderstood my 'Please, please, please!!!' ... > Indeed. I did. "Please, please, please!!!" sounds very demanding to me. :) > I wasn't > insisting/demanding, I was begging... so, your snipe about 'becoming a > developer was, I think, a bit uncalled for. > Okay. Now I understand. I am just a normal user as you are. But I often see people just asking, asking and asking but not taking the small step to give anything back. That's the reason for my response. Making an overlay with the version in question is really no big thing. At least it is not a big thing if you really need the specific version.
(In reply to comment #11) >> That said - updating packages that are in portage is [relatively] easy - >> setting up a local overlay is not something I am prepared to do at the >> moment. I've read about it, and see the potential benefit - but it adds a >> level of complexity I'm not prepared to accept now. > It is not so complex. Just some small work and responsibility. That's all :) Ok, fair enough - maybe I'll take another look and give it a shot... may even have time to do that today. >> Maybe you misunderstood my 'Please, please, please!!!' ... > Indeed. I did. "Please, please, please!!!" sounds very demanding to me. :) But you didn't see me bowing in subservience to the ebuild gods... ;) Anyway, I know it sounds lame, but as I said - I'm not a programmer, otherwise I would be happy to help out and attach updated ebuilds, but... At the time I first commented, it still wouldn't have seemed necessary to do so since the *apparently* trivial work in updating this ebuild for the official repository (for someone who knows how to maintain ebuilds) has already been done by you (and Conrad)... Yes, as you pointed out, I can make the change myself, but all I'd be doing is monkey-copying the changes posted here, but I much prefer to leave things like that in the hands of the experts... :) Is Robin awol? Is courier-imap actually absent a maintainer? If so, shouldn't this bug be 'unassigned'? If it was, then it would certainly be inappropriate to 'beg' here, and more appropriate to offer to take it over, assuming some minimal qualifications which I obviously don't have, in which case I'd have just kept my mouth shut... Anyway, thanks for the kick in the pants to take another look at setting up a local mirror and custom overlay - never know when it might come in handy again. NOTE: I see that dovecot is being actively maintained, with ebuilds appearing within a day or two of releases - even the latest betas of the new 1.1 version are in unstable - maybe its time to switch? :)
(In reply to comment #12) > (In reply to comment #11) > >> That said - updating packages that are in portage is [relatively] easy - > >> setting up a local overlay is not something I am prepared to do at the > >> moment. I've read about it, and see the potential benefit - but it adds a > >> level of complexity I'm not prepared to accept now. > > > It is not so complex. Just some small work and responsibility. That's all :) > > Ok, fair enough - maybe I'll take another look and give it a shot... may even > have time to do that today. > > >> Maybe you misunderstood my 'Please, please, please!!!' ... > > > Indeed. I did. "Please, please, please!!!" sounds very demanding to me. :) > > But you didn't see me bowing in subservience to the ebuild gods... ;) > LOL > Anyway, I know it sounds lame, but as I said - I'm not a programmer, otherwise > I would be happy to help out and attach updated ebuilds, but... > > At the time I first commented, it still wouldn't have seemed necessary to do so > since the *apparently* trivial work in updating this ebuild for the official > repository (for someone who knows how to maintain ebuilds) has already been > done by you (and Conrad)... > Okay. If it is all about ebuilds, then I will post the full blown up 4.3.0 including the patches... > Yes, as you pointed out, I can make the change myself, but all I'd be doing is > monkey-copying the changes posted here, but I much prefer to leave things like > that in the hands of the experts... :) > > Is Robin awol? Is courier-imap actually absent a maintainer? > I don't know. > If so, shouldn't > this bug be 'unassigned'? If it was, then it would certainly be inappropriate > to 'beg' here, and more appropriate to offer to take it over, assuming some > minimal qualifications which I obviously don't have, in which case I'd have > just kept my mouth shut... > > Anyway, thanks for the kick in the pants to take another look at setting up a > local mirror and custom overlay - never know when it might come in handy again. > > NOTE: I see that dovecot is being actively maintained, with ebuilds appearing > within a day or two of releases - even the latest betas of the new 1.1 version > are in unstable - maybe its time to switch? :) > It is different from package to package from maintainer to maintainer. Some packages are slowly being updated to new versions while others are very fast updated. I don't know the reason for that but I suspect the lack of developers and/or lack of commitment to be the problem. But this is just an assumption. I don't know the real reason for the delay. // SteveB
Created attachment 139730 [details] net-mail/courier-imap/courier-imap-4.3.0.ebuild Ebuild for courier-imap-4.3.0. Just copy it into your portage overlay into <portage overlay dir>net-mail/courier-imap/courier-imap-4.3.0.ebuild
Created attachment 139731 [details, diff] net-mail/courier-imap/files/courier-imap-4.3.0-as-needed.patch Copy it into your portage overlay: <portage overlay directory>/net-mail/courier-imap/files/courier-imap-4.3.0-as-needed.patch
Don't forget to copy the stuff from /usr/portage/net-mail/courier-imap/files/ to <your overlay directory>/net-mail/courier-imap/files/ and then just execute "ebuild <your overlay directory>/net-mail/courier-imap/courier-imap-4.3.0.ebuild digest" to create the digest and then you are ready to install courier-imap-4.3.0 :) // SteveB
Ok... first dumb question... ;) Why does this ebuild only reference 4.0.6-r1? I'd have ass-u-me-d that it would be 4.3.0... ?
(In reply to comment #17) > Ok... first dumb question... ;) > > Why does this ebuild only reference 4.0.6-r1? I'd have ass-u-me-d that it would > be 4.3.0... ? > What do you mean? The stuff from FILESDIR? Well... some scripts/patches are still valid for 4.3.0. And since they can/are applied without any changes... why producing new ones with version 4.3.0 (saving space in Portage is not a bad thing :))? // SteveB
Oh, ok... thanks!
(In reply to comment #16) > Don't forget to copy the stuff from /usr/portage/net-mail/courier-imap/files/ > to <your overlay directory>/net-mail/courier-imap/files/ Aaargh! Of course, I missed that, and went straight to executing the ebuild ... digest command. > and then just execute "ebuild <your overlay > directory>/net-mail/courier-imap/courier-imap-4.3.0.ebuild digest" to create > the digest It downloaded the source and appeared to complete ok... ? Should I delete the 'files' dir and 'Manifest' file it created and redo this step? > and then you are ready to install courier-imap-4.3.0 :) Sorry for being in such a hurry and failing to follow directions - I usually don't miss stuff like that.
(In reply to comment #20) > (In reply to comment #16) > > Don't forget to copy the stuff from /usr/portage/net-mail/courier-imap/files/ > > to <your overlay directory>/net-mail/courier-imap/files/ > > Aaargh! Of course, I missed that, and went straight to executing the ebuild > ... digest command. > :) > > and then just execute "ebuild <your overlay > > directory>/net-mail/courier-imap/courier-imap-4.3.0.ebuild digest" to create > > the digest > > It downloaded the source and appeared to complete ok... ? Should I delete the > 'files' dir and 'Manifest' file it created and redo this step? > If you have copied the files from /usr/portage/net-mail/courier-imap/files to the directory files in your overlay, then just redo the ebuild .... digest stuff and all should/will be okay. Then just emerge the new courier-imap: emerge -v =net-mail/courier-imap-4.3.0 > > and then you are ready to install courier-imap-4.3.0 :) > > Sorry for being in such a hurry and failing to follow directions - I usually > don't miss stuff like that. > Ach! Don't apologize. It is not needed :) Every one of us stepped once into that trap. You are not the first and will not be the last :) // SteveB
Ok - I just copied them over. The only file that was in there (the new local overlay) was the digest file... Just to confirm... there is NO digest file in the /usr/portage courier-imap/files directory, right? This digest file is in the /user/local/portage courier-imap/files directory because this is a local overlay? Here is the current directory listing: myhost files # pwd /usr/local/portage/net-mail/courier-imap/files myhost files # ls -al total 215 drwxr-xr-x 2 root root 3000 Dec 31 13:12 . drwxr-xr-x 3 root root 200 Dec 31 12:37 .. -rw-r--r-- 1 root root 1062 Dec 31 13:12 authdaemond-3.0.4-r1 -rw-r--r-- 1 root root 544 Dec 31 13:12 authdaemond.conf-3.0.4-r1 -rw-r--r-- 1 root root 1263 Dec 31 13:12 courier-imap-3.0.8-db4-bdbobj_configure.in.patch -rw-r--r-- 1 root root 1337 Dec 31 13:12 courier-imap-3.0.8-db4-configure.in.patch -rw-r--r-- 1 root root 654 Dec 31 13:12 courier-imap-3.0.8-disable-fam-configure.in.patch -rw-r--r-- 1 root root 1215 Dec 31 13:12 courier-imap-4.0.1-courier-imapd-ssl.rc6 -rw-r--r-- 1 root root 970 Dec 31 13:12 courier-imap-4.0.1-courier-imapd.rc6 -rw-r--r-- 1 root root 1223 Dec 31 13:12 courier-imap-4.0.1-courier-pop3d-ssl.rc6 -rw-r--r-- 1 root root 978 Dec 31 13:12 courier-imap-4.0.1-courier-pop3d.rc6 -rw-r--r-- 1 root root 1263 Dec 31 13:12 courier-imap-4.0.1-db4-bdbobj_configure.in.patch -rw-r--r-- 1 root root 1303 Dec 31 13:12 courier-imap-4.0.1-db4-configure.in.patch -rw-r--r-- 1 root root 654 Dec 31 13:12 courier-imap-4.0.1-disable-fam-configure.in.patch -rw-r--r-- 1 root root 1092 Dec 31 13:12 courier-imap-4.0.1-gentoo-imapd-ssl.rc -rw-r--r-- 1 root root 1129 Dec 31 13:12 courier-imap-4.0.1-gentoo-imapd.rc -rw-r--r-- 1 root root 1067 Dec 31 13:12 courier-imap-4.0.1-gentoo-pop3d-ssl.rc -rw-r--r-- 1 root root 1075 Dec 31 13:12 courier-imap-4.0.1-gentoo-pop3d.rc -rw-r--r-- 1 root root 85 Dec 31 13:12 courier-imap-4.0.1-r1-courier-imapd.indirect -rw-r--r-- 1 root root 85 Dec 31 13:12 courier-imap-4.0.1-r1-courier-pop3d.indirect -rw-r--r-- 1 root root 1114 Dec 31 13:12 courier-imap-4.0.1-r1-gentoo-imapd-ssl.rc -rw-r--r-- 1 root root 1151 Dec 31 13:12 courier-imap-4.0.1-r1-gentoo-imapd.rc -rw-r--r-- 1 root root 1089 Dec 31 13:12 courier-imap-4.0.1-r1-gentoo-pop3d-ssl.rc -rw-r--r-- 1 root root 1097 Dec 31 13:12 courier-imap-4.0.1-r1-gentoo-pop3d.rc -rw-r--r-- 1 root root 1174 Dec 31 13:12 courier-imap-4.0.4-courier-imapd-ssl.rc6 -rw-r--r-- 1 root root 929 Dec 31 13:12 courier-imap-4.0.4-courier-imapd.rc6 -rw-r--r-- 1 root root 1182 Dec 31 13:12 courier-imap-4.0.4-courier-pop3d-ssl.rc6 -rw-r--r-- 1 root root 937 Dec 31 13:12 courier-imap-4.0.4-courier-pop3d.rc6 -rw-r--r-- 1 root root 237 Dec 31 13:12 courier-imap-4.0.6-aclocal-fix.patch -rw-r--r-- 1 root root 1558 Dec 31 13:12 courier-imap-4.0.6-db4-bdbobj_configure.in.patch -rw-r--r-- 1 root root 1497 Dec 31 13:12 courier-imap-4.0.6-db4-configure.in.patch -rw-r--r-- 1 root root 264 Dec 31 13:12 courier-imap-4.0.6-db4-tcpd_configure.in.patch -rw-r--r-- 1 root root 1200 Dec 31 13:12 courier-imap-4.0.6-r1-courier-imapd-ssl.rc6 -rw-r--r-- 1 root root 81 Dec 31 13:12 courier-imap-4.0.6-r1-courier-imapd.indirect -rw-r--r-- 1 root root 949 Dec 31 13:12 courier-imap-4.0.6-r1-courier-imapd.rc6 -rw-r--r-- 1 root root 1208 Dec 31 13:12 courier-imap-4.0.6-r1-courier-pop3d-ssl.rc6 -rw-r--r-- 1 root root 81 Dec 31 13:12 courier-imap-4.0.6-r1-courier-pop3d.indirect -rw-r--r-- 1 root root 957 Dec 31 13:12 courier-imap-4.0.6-r1-courier-pop3d.rc6 -rw-r--r-- 1 root root 984 Dec 31 13:12 courier-imap-4.0.6-r1-gentoo-imapd-ssl.rc -rw-r--r-- 1 root root 1026 Dec 31 13:12 courier-imap-4.0.6-r1-gentoo-imapd.rc -rw-r--r-- 1 root root 957 Dec 31 13:12 courier-imap-4.0.6-r1-gentoo-pop3d-ssl.rc -rw-r--r-- 1 root root 999 Dec 31 13:12 courier-imap-4.0.6-r1-gentoo-pop3d.rc -rw-r--r-- 1 root root 398 Dec 31 13:12 courier-imap-4.1.2-as-needed.patch -rw-r--r-- 1 root root 2827 Dec 31 13:12 courier-imap-gentoo.readme -rw-r--r-- 1 root root 1196 Dec 31 13:12 courier-imapd-ssl.rc6-3.0.5 -rwxr-xr-x 1 root root 945 Dec 31 13:12 courier-imapd.rc6 -rw-r--r-- 1 root root 1204 Dec 31 13:12 courier-pop3d-ssl.rc6-3.0.5 -rwxr-xr-x 1 root root 953 Dec 31 13:12 courier-pop3d.rc6 -rw-r--r-- 1 root root 262 Dec 31 12:37 digest-courier-imap-4.3.0 -rwxr-xr-x 1 root root 1074 Dec 31 13:12 gentoo-imapd-1.7.3-r1.rc -rwxr-xr-x 1 root root 1036 Dec 31 13:12 gentoo-imapd-ssl-1.7.3-r1.rc -rwxr-xr-x 1 root root 1020 Dec 31 13:12 gentoo-pop3d-1.7.3-r1.rc -rwxr-xr-x 1 root root 1012 Dec 31 13:12 gentoo-pop3d-ssl-1.7.3-r1.rc -rwxr-xr-- 1 root root 996 Dec 31 13:12 mkimapdcert -rwxr-xr-x 1 root root 996 Dec 31 13:12 mkpop3dcert myhost files #
So - do I need to redo the digest command now?
(In reply to comment #23) > So - do I need to redo the digest command now? > YES
(In reply to comment #24) > (In reply to comment #23) > > So - do I need to redo the digest command now? > > > YES > The Gentoo Bugzilla people will kill us for degrading/misusing Bugzilla to/as a forum :)
(In reply to comment #25) > > YES > > > The Gentoo Bugzilla people will kill us for degrading/misusing Bugzilla to/as a > forum :) ... and if you know you're doing something "wrong" - why are you doing it? It's not that we don't have forums exactly for things like this ;)
(In reply to comment #26) > (In reply to comment #25) > > > YES > > > > > The Gentoo Bugzilla people will kill us for degrading/misusing Bugzilla to/as a > > forum :) > > ... and if you know you're doing something "wrong" - why are you doing it? > @Tobias: Relax. I don't think that Charles intention was to misuse Bugzilla. I did not want to misuse it as well. I just replied to each post and then I realized that we are drifting away from the main purpose of this bug report. So I just mentioned the misuse thing because I felt that this ping pong/chit chat in Bugzilla is the wrong approach. Meanwhile Charles contacted me by email and we are going to sort his problems over email. > It's > not that we don't have forums exactly for things like this ;) > I know. btw: What is the state for courier-imap? Why is it taking so long to get simple version bumps into portage? Is there any thing we/(I) could do to get that faster forward? Ich wünsche Dir und Deiner Familie einen guten Rutsch in das neue Jahr 2008. Grüsse aus Zürich. // Steve
Ok, just for future reference, with Steve's help and recommendations (just following what he posted here - no further help necessary), I'm now running 4.3 from my new local overlay... Thanks Steve!!
To any one installing 4.3.0: Please be so kind and post here back if you have problems or no problems with 4.3.0. The more qualified information the maintainer for Courier IMAP has, the easier we as the Gentoo community can make it for him/her to decide if and when to push a new ebuild into portage.
One thing I forgot to mention... I was getting some of these errors after restarting courier-imap: imapd-ssl: couriertls: connect: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Found the fix here: http://tinyurl.com/2g9qog Short of it is, edit /etc/courier/imapd-ssl, and change TLS_PROTOCOL to SSL23 instead of just SSL3...
Forgot - my platform is amd64...
(In reply to comment #30) > One thing I forgot to mention... > > I was getting some of these errors after restarting courier-imap: > > imapd-ssl: couriertls: connect: error:1408F10B:SSL > routines:SSL3_GET_RECORD:wrong version number > > Found the fix here: http://tinyurl.com/2g9qog > > Short of it is, edit /etc/courier/imapd-ssl, and change TLS_PROTOCOL to SSL23 > instead of just SSL3... > This guy is wrong. When using the Gentoo ebuild then the changes in /etc/courier-imap/imapd-ssl get pulled in and after etc-update the options are updated: ##NAME: TLS_PROTOCOL:0 # # TLS_PROTOCOL sets the protocol version. The possible versions are: # # OpenSSL: # # SSL2 - SSLv2 # SSL3 - SSLv3 # SSL23 - either SSLv2 or SSLv3 # TLS1 - TLS1 # # GnuTLS: # # SSL3 - SSLv3 # TLS1 - TLS 1.0 # TLS1_1 TLS 1.1 # # When compiled against GnuTLS, multiple protocols can be selected as follows: # # TLS_PROTOCOL="TLS1_1:TLS1:SSL3" So we are not affected by this error found on Ubuntu. You got to love Portage for the flexibility and diversity it has :) // SteveB
Ok, well, then, I'm not sure how I got bit... When I ran etc-update, mine was already set to just SSL3 (I just confirmed this by looking at the backup I made immediately before doing this) - but was NOT exhibiting this problem. After the update to 4.3, I started getting the problem - and changing this to SSL23 fixed it... So, I guess 'the question' is, why was I NOT getting the error prior to upgrading? The only answer I could come up with is something is different with 4.3... but I could easily be wrong... ;)
(In reply to comment #33) > Ok, well, then, I'm not sure how I got bit... > > When I ran etc-update, mine was already set to just SSL3 (I just confirmed this > by looking at the backup I made immediately before doing this) - but was NOT > exhibiting this problem. > You got me wrong. I was referring to the statement below taken from the URL you posted: > courier-imap-ssl broke. My cell phone could no longer pull mail. > I got something like in the log: > imapd-ssl: couriertls: connect: > error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number > The fix for this is to change the TLS_PROTOCOL option in > /etc/courier/imapd-ssl to SSL23 (an option not listed in the > “possible verions” list in the config file). So mail now works. > Option not listed in the "possible versions"? That is simply not true. Not true for a proper installation as we have it in Gentoo. And I did not question your need for enabling SSLv2 and SSLv3. And I did not question that etc-update did not change your TLS_PROTOCOL from TLS_PROTOCOL=SSL3 to TLS_PROTOCOL=SSL23. I personally don't see a need for Portage or the Ebuild to do that change. It could be done very easy but why? Users need to read the documentation and change log and if they need SSLv2, then it is their responsibility to enable it. It is like enabling SSHv1 in the SSH daemon. If some one really needs it, then he/her should enable it. But Gentoo Portage/Ebuild should not weaken the system by default for nothing. > After the update to 4.3, I started getting the problem - and changing this to > SSL23 fixed it... > I believe you. You just enabled SSLv2 and SSLv3 and before you only had SSLv3 and your client did not work with just SSLv3 and the new Courier IMAP version. > So, I guess 'the question' is, why was I NOT getting the error prior to > upgrading? The only answer I could come up with is something is different with > 4.3... but I could easily be wrong... ;) > Yes. Many things have changed in Courier for SSL/TLS. I don't know the answer why it worked before. I would need to look into the code to see what was before there and what is now there. But I don't have the time to dig that deep into the code. I assume that before the SSL implementation worked with SSLv2 even if you have enabled just SSLv3 and now the new version fixes that and forces you to explicitly configure/enable SSLv2 (with or without SSLv3) if you need it. But this is an assumption.
(In reply to comment #34) > You got me wrong. I was referring to the statement below taken from the URL > you posted: >> The fix for this is to change the TLS_PROTOCOL option in >> /etc/courier/imapd-ssl to SSL23 (an option not listed in the >> “possible verions” list in the config file). So mail now works. > Option not listed in the "possible versions"? Ahh... ok, missed that... you're right of course, the new comments listing all of the options were definitely there (I had to merge them of course). > And I did not question your need for enabling SSLv2 and SSLv3. And I did not > question that etc-update did not change your TLS_PROTOCOL from > TLS_PROTOCOL=SSL3 to TLS_PROTOCOL=SSL23. I personally don't see a need for > Portage or the Ebuild to do that change. Sorry, you misunderstood my comment... I wasn't complaining, and I agree that it isn't portage's job to make config changes for me... The 'question' I posed was more just me wondering out loud why restricting to SSL3 only would work ok with 4.0.6, but not for 4.3 - usually it is the other way around (newer versions have better support for existing protocols). The main reason I added my note about this was for anyone else who might decide to use your ebuild to update. You did specifically ask for everyone to comment on whether or not they had any problems... ;) > I assume that before the SSL implementation worked with SSLv2 even if you > have enabled just SSLv3 and now the new version fixes that and forces you > to explicitly configure/enable SSLv2 (with or without SSLv3) if you need it. > But this is an assumption. And probably a good one... Thanks again for uploading your ebuild... hopefully this will make it into the portage tree sooner or later...
Upgraded to 4.3.0 using the posted ebuild + patch. Builds fine. Works fine. The only difference I noticed is that the initial upgrade broke ssl. I set TLS_PROTOCOL to SSL23. TLS_PROTOCOL was set to SSL3 before the upgrade. Why would this occur? Other than that, all else appears to function as expected.
Hi Juan, Not to be rude, but I'm curious why you would take the time to post your comment here, but not take the time to actually READ THE PREVIOUS COMMENTS? Your question is already answered.
So, is this package going to hit portage?
(In reply to comment #38) > So, is this package going to hit portage? > Just relax. It will hit portage when it is ready to hit portage. In the meantime you can use the procedure described here in this bug report if you need the package.
*g* As i am the reporter, i am using it since in my overlay ;)
(In reply to comment #40) > *g* > > As i am the reporter, i am using it since in my overlay ;) > I know that you are the reporter :). In Gentoo land things have slowed down (this is my personal feeling) and you have to wait. That's the way it works. Unfortunately. btw: Einen Tag zu spät aber dennoch: Alles gute zum Geburtstag (ich glaube Du hattest Geburtstag am 26sten?)
Hola! Jetzt hast du mich überrascht *g* (Dass du das gemerkt hast :D) Ich danke für die Glückwünsche :) Yes i know, that things slowed down here :( But sometimes, this anoyes me very ... And in this case, it seems to be a standard version bump, nothing complicated ... Would be cool if Robin whould say something about the status, so we know whats going on.
I'm busy with a lot of other things in Infra. courier-imap(CI) is really low on my priority list - my existing CI works, and I don't have a need to re-install it YET. This will differ in a couple of weeks, as I have to build a new 1U server for myself, so a new CI will probably end up in the tree around then.
I've installed and used courier-imap-4.3.0 and courier-authlib-0.60.2 for about a week now without any problems on a x86_64 hardened system (no 32-bit userland).
Any new News Robin?
Created attachment 147108 [details] net-mail/courier-imap/courier-imap-4.3.1.ebuild
Created attachment 147110 [details, diff] net-mail/courier-imap/files/courier-imap-4.3.1-as-needed.patch
Thanks steveb :) Works fine here your ebuilds. What about Robin? Any Updates planed?
I need help :( I am not able to compile courier-imap 4.3.1 with libtool 2.2.4. It always fails. Accoring to Bug #226127 there is a solution for 4.1.2, but this does not work for me :(
Ok, it seems a little bit my fault ;) ccache was the fault. With this updated ebuild, it works with libtool 2.2.4 fine.
Created attachment 158489 [details] courier-imap-4.3.1.ebuild Updated ebuild to work with libtool 2.2.4
Meanwhile the 4.4.0 version is out.
Created attachment 160343 [details] courier-imap-4.4.0.ebuild Newest courier-imap-4.4.0.ebuild :) There patches are dropped, as there are now part of upstream: courier-imap-4.1.2-as-needed.patch (and courier-imap-4.3.1-as-needed.patch) courier-imap-4.0.6-db4-tcpd_configure.in.patch This works fine here for me and compiles :)
Created attachment 160345 [details] courier-imap-4.4.0.ebuild.patch courier-imap-4.4.0.ebuild.patch Diff against courier-imap-4.1.2-r1.ebuild
Created attachment 160347 [details] courier-imap-4.4.0.ebuild sry, new ebuild. forgot got change depencies. courier-authlib 0.61.0 is needed now. See Bug #231770
Created attachment 160349 [details, diff] courier-imap-4.4.0.ebuild.patch sry, new ebuild patch. forgot got change depencies. courier-authlib 0.61.0 is needed now. See Bug #231770
There seems some problems with libtool and courier-imap 4.4.0. I don't know how to reproduce this. On my Main Gentoo, it works fine with compiling. My second gentoo machine fails :( Anybody got an Idea? Making all in maildir make[2]: Entering directory `/var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0/maildir' echo '#define MAILDIRSHAREDRC "/etc/courier-imap/maildirshared"' >maildirsharedrc.h echo '#define MAILDIRFILTERCONFIG "/etc/courier-imap/maildirfilterconfig"' >maildirfilterconfig.h echo '#define QUOTAWARNMSG "/etc/courier-imap/quotawarnmsg"' >quotawarnmsg.h echo '#define MAILBOT "mailbot"' >mailbot.h echo '#define AUTORESPONSEQUOTA "/etc/courier-imap/autoresponsesquota"' >autoresponsequota.h CONFIG_FILES=deliverquota.html CONFIG_HEADERS= /bin/sh ./config.status CONFIG_FILES=maildirmake.html CONFIG_HEADERS= /bin/sh ./config.status config.status: creating deliverquota.html config.status: creating maildirmake.html config.status: executing depfiles commands config.status: executing depfiles commands config.status: executing libtool commands config.status: executing libtool commands mv: cannot stat `libtoolT': No such file or directory cp: CONFIG_FILES=deliverquota.8 CONFIG_HEADERS= /bin/sh ./config.status cannot stat `libtoolT': No such file or directory chmod: cannot access `libtool': No such file or directory CONFIG_FILES=maildirmake.1 CONFIG_HEADERS= /bin/sh ./config.status config.status: creating deliverquota.8 config.status: creating maildirmake.1 config.status: executing depfiles commands config.status: executing libtool commands config.status: executing depfiles commands config.status: executing libtool commands CONFIG_FILES=maildiracl.html CONFIG_HEADERS= /bin/sh ./config.status CONFIG_FILES=maildiracl.1 CONFIG_HEADERS= /bin/sh ./config.status config.status: creating maildiracl.html config.status: creating maildiracl.1 config.status: executing depfiles commands config.status: executing libtool commands config.status: executing depfiles commands config.status: executing libtool commands echo >maildir.libdeps make all-am make[3]: Entering directory `/var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0/maildir' /bin/sh ./libtool --tag=CC --mode=compile i586-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -march=geode -Os -mmmx -m3dnow -fno-align-jumps -fno-align-functions -fno-align-labels -fno-align-loops -pipe -fomit-frame-pointer -mfpmath=387 -Wall -I./.. -I.. -MT autoresponse.lo -MD -MP -MF .deps/autoresponse.Tpo -c -o autoresponse.lo autoresponse.c /bin/sh ./libtool --tag=CC --mode=compile i586-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -march=geode -Os -mmmx -m3dnow -fno-align-jumps -fno-align-functions -fno-align-labels -fno-align-loops -pipe -fomit-frame-pointer -mfpmath=387 -Wall -I./.. -I.. -MT maildiraclt.lo -MD -MP -MF .deps/maildiraclt.Tpo -c -o maildiraclt.lo maildiraclt.c ./libtool: line 13: func_dirname_and_basename: command not found ./libtool: line 13: func_dirname_and_basename: command not found /var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0/maildir/: /var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0/maildir/: is a directory make[3]: *** [autoresponse.lo] Error 126 make[3]: *** Waiting for unfinished processes... /var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0/maildir/: /var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0/maildir/: is a directory make[3]: *** [maildiraclt.lo] Error 126 make[3]: Leaving directory `/var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0/maildir' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0/maildir' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/net-mail/courier-imap-4.4.0/work/courier-imap-4.4.0' make: *** [all] Error 2
(In reply to comment #57) > There seems some problems with libtool and courier-imap 4.4.0. > I don't know how to reproduce this. On my Main Gentoo, it works fine with > compiling. My second gentoo machine fails :( > > Anybody got an Idea? > Could you post the output of libtool --config
(In reply to comment #58) > Could you post the output of libtool --config > Sure, here we go: # Which release of libtool.m4 was used? macro_version=2.2.4 macro_revision=1.2976 # Assembler program. AS=as # DLL creation program. DLLTOOL=dlltool # Object dumper program. OBJDUMP=objdump # Whether or not to build shared libraries. build_libtool_libs=yes # Whether or not to build static libraries. build_old_libs=yes # What type of objects to build. pic_mode=default # Whether or not to optimize for fast installation. fast_install=needless # The host system. host_alias=i586-pc-linux-gnu host=i586-pc-linux-gnu host_os=linux-gnu # The build system. build_alias=i586-pc-linux-gnu build=i586-pc-linux-gnu build_os=linux-gnu # A sed program that does not truncate output. SED="/bin/sed" # Sed that helps us avoid accidentally triggering echo(1) options like -n. Xsed="$SED -e 1s/^X//" # A grep program that handles long lines. GREP="/bin/grep" # An ERE matcher. EGREP="/bin/grep -E" # A literal string matcher. FGREP="/bin/grep -F" # A BSD- or MS-compatible name lister. NM="/usr/bin/nm -B" # Whether we need soft or hard links. LN_S="ln -s" # What is the maximum length of a command? max_cmd_len=98304 # Object file suffix (normally "o"). objext=o # Executable file suffix (normally ""). exeext= # whether the shell understands "unset". lt_unset=unset # turn spaces into newlines. SP2NL="tr \\040 \\012" # turn newlines into spaces. NL2SP="tr \\015\\012 \\040\\040" # How to create reloadable object files. reload_flag=" -r" reload_cmds="\$LD\$reload_flag -o \$output\$reload_objs" # Method to check whether dependent libraries are shared objects. deplibs_check_method="pass_all" # Command to use when deplibs_check_method == "file_magic". file_magic_cmd="\$MAGIC_CMD" # The archiver. AR="i586-pc-linux-gnu-ar" AR_FLAGS="cru" # A symbol stripping program. STRIP="i586-pc-linux-gnu-strip" # Commands used to install an old-style archive. RANLIB="i586-pc-linux-gnu-ranlib" old_postinstall_cmds="chmod 644 \$oldlib~\$RANLIB \$oldlib" old_postuninstall_cmds="" # A C compiler. LTCC="i586-pc-linux-gnu-gcc" # LTCC compiler flags. LTCFLAGS="-march=geode -Os -mmmx -m3dnow -fno-align-jumps -fno-align-functions -fno-align-labels -fno-align-loops -pipe -fomit-frame-poi nter -mfpmath=387" # Take the output of nm and produce a listing of raw symbols and C names. global_symbol_pipe="sed -n -e 's/^.*[ ]\\([ABCDGIRSTW][ABCDGIRSTW]*\\)[ ][ ]*\\([_A-Za-z][_A-Za-z0-9]*\\)\$/\\1 \\2 \\2/p' " # Transform the output of nm in a proper C declaration. global_symbol_to_cdecl="sed -n -e 's/^T .* \\(.*\\)\$/extern int \\1();/p' -e 's/^[ABCDGIRSTW]* .* \\(.*\\)\$/extern char \\1;/p'" # Transform the output of nm in a C name address pair. global_symbol_to_c_name_address="sed -n -e 's/^: \\([^ ]*\\) \$/ {\\\"\\1\\\", (void *) 0},/p' -e 's/^[ABCDGIRSTW]* \\([^ ]*\\) \\([^ ] *\\)\$/ {\"\\2\", (void *) \\&\\2},/p'" # Transform the output of nm in a C name address pair when lib prefix is needed. global_symbol_to_c_name_address_lib_prefix="sed -n -e 's/^: \\([^ ]*\\) \$/ {\\\"\\1\\\", (void *) 0},/p' -e 's/^[ABCDGIRSTW]* \\([^ ]* \\) \\(lib[^ ]*\\)\$/ {\"\\2\", (void *) \\&\\2},/p' -e 's/^[ABCDGIRSTW]* \\([^ ]*\\) \\([^ ]*\\)\$/ {\"lib\\2\", (void *) \\&\\2},/p' " # The name of the directory that contains temporary libtool files. objdir=.libs # Shell to use when invoking shell scripts. SHELL="/bin/sh" # An echo program that does not interpret backslashes. ECHO="echo" # Used to examine libraries when file_magic_cmd begins with "file". MAGIC_CMD=file # Must we lock files when doing compilation? need_locks="no" # Tool to manipulate archived DWARF debug symbol files on Mac OS X. DSYMUTIL="" # Tool to change global to local symbols on Mac OS X. NMEDIT="" # Tool to manipulate fat objects and archives on Mac OS X. LIPO="" # ldd/readelf like tool for Mach-O binaries on Mac OS X. OTOOL="" # ldd/readelf like tool for 64 bit Mach-O binaries on Mac OS X 10.4. OTOOL64="" # Old archive suffix (normally "a"). libext=a # Shared library suffix (normally ".so"). shrext_cmds=".so" # The commands to extract the exported symbol list from a shared archive. extract_expsyms_cmds="" # Variables whose values should be saved in libtool wrapper scripts and # restored at link time. variables_saved_for_relink="PATH LD_LIBRARY_PATH LD_RUN_PATH GCC_EXEC_PREFIX COMPILER_PATH LIBRARY_PATH" # Do we need the "lib" prefix for modules? need_lib_prefix=no # Do we need a version for libraries? need_version=no # Library versioning type. version_type=linux # Shared library runtime path variable. runpath_var=LD_RUN_PATH # Shared library path variable. shlibpath_var=LD_LIBRARY_PATH # Is shlibpath searched before the hard-coded library search path? shlibpath_overrides_runpath=yes # Format of library name prefix. libname_spec="lib\$name" # List of archive names. First name is the real one, the rest are links. # The last name is the one that the linker finds with -lNAME library_names_spec="\${libname}\${release}\${shared_ext}\$versuffix \${libname}\${release}\${shared_ext}\$major \$libname\${shared_ext}" # The coded name of the library, if different from the real name. soname_spec="\${libname}\${release}\${shared_ext}\$major" # Command to use after installation of a shared archive. postinstall_cmds="" # Command to use after uninstallation of a shared archive. postuninstall_cmds="" # Commands used to finish a libtool library installation in a directory. finish_cmds="PATH=\\\"\\\$PATH:/sbin\\\" ldconfig -n \$libdir" # As "finish_cmds", except a single script fragment to be evaled but # not shown. finish_eval="" # Whether we should hardcode library paths into libraries. hardcode_into_libs=yes # Compile-time system search path for libraries. sys_lib_search_path_spec="/usr/lib/gcc/i586-pc-linux-gnu/4.3.1 /usr/i586-pc-linux-gnu/lib /usr/lib /lib" # Run-time system search path for libraries. sys_lib_dlsearch_path_spec="/lib /usr/lib /usr/local/lib /usr/i586-pc-linux-gnu/lib /usr/lib/gcc/i586-pc-linux-gnu/4.3.1 " # Whether dlopen is supported. dlopen_support=yes # Whether dlopen of programs is supported. dlopen_self=yes # Whether dlopen of statically linked programs is supported. dlopen_self_static=no # Commands to strip libraries. old_striplib="i586-pc-linux-gnu-strip --strip-debug" striplib="i586-pc-linux-gnu-strip --strip-unneeded" # The linker used to build libraries. LD="/usr/i586-pc-linux-gnu/bin/ld" # Commands used to build an old-style archive. old_archive_cmds="\$AR \$AR_FLAGS \$oldlib\$oldobjs~\$RANLIB \$oldlib" # A language specific compiler. CC="i586-pc-linux-gnu-gcc" # Is the compiler the GNU compiler? with_gcc=yes # Compiler flag to turn off builtin functions. no_builtin_flag=" -fno-builtin" # How to pass a linker flag through the compiler. wl="-Wl," # Additional compiler flags for building library objects. pic_flag=" -fPIC -DPIC" # Compiler flag to prevent dynamic linking. link_static_flag="-static" # Does compiler simultaneously support -c and -o options? compiler_c_o="yes" # Whether or not to add -lc for building shared libraries. build_libtool_need_lc=no # Whether or not to disallow shared libs when runtime libs are static. allow_libtool_libs_with_static_runtimes=no # Compiler flag to allow reflexive dlopens. export_dynamic_flag_spec="\${wl}--export-dynamic" # Compiler flag to generate shared objects directly from archives. whole_archive_flag_spec="\${wl}--whole-archive\$convenience \${wl}--no-whole-archive" # Whether the compiler copes with passing no objects directly. compiler_needs_object="no" # Create an old-style archive from a shared archive. old_archive_from_new_cmds="" # Create a temporary old-style archive to link instead of a shared archive. old_archive_from_expsyms_cmds="" # Commands used to build a shared archive. archive_cmds="\$CC -shared \$libobjs \$deplibs \$compiler_flags \${wl}-soname \$wl\$soname -o \$lib" archive_expsym_cmds="echo \\\"{ global:\\\" > \$output_objdir/\$libname.ver~ cat \$export_symbols | sed -e \\\"s/\\\\(.*\\\\)/\\\\1;/\\\" >> \$output_objdir/\$libname.ver~ echo \\\"local: *; };\\\" >> \$output_objdir/\$libname.ver~ \$CC -shared \$libobjs \$deplibs \$compiler_flags \${wl}-soname \$wl\$soname \${wl}-version-script \${wl}\$output_objdir/\$l ibname.ver -o \$lib" # Commands used to build a loadable module if different from building # a shared archive. module_cmds="" module_expsym_cmds="" # Whether we are building with GNU ld or not. with_gnu_ld="yes" # Flag that allows shared libraries with undefined symbols to be built. allow_undefined_flag="" # Flag that enforces no undefined symbols. no_undefined_flag="" # Flag to hardcode $libdir into a binary during linking. # This must work even if $libdir does not exist hardcode_libdir_flag_spec="\${wl}-rpath \${wl}\$libdir" # If ld is used when linking, flag to hardcode $libdir into a binary # during linking. This must work even if $libdir does not exist. hardcode_libdir_flag_spec_ld="" # Whether we need a single "-rpath" flag with a separated argument. hardcode_libdir_separator="" # Set to "yes" if using DIR/libNAME${shared_ext} during linking hardcodes # DIR into the resulting binary. hardcode_direct=no # Set to "yes" if using DIR/libNAME${shared_ext} during linking hardcodes # DIR into the resulting binary and the resulting library dependency is # "absolute",i.e impossible to change by setting ${shlibpath_var} if the # library is relocated. hardcode_direct_absolute=no # Set to "yes" if using the -LDIR flag during linking hardcodes DIR # into the resulting binary. hardcode_minus_L=no # Set to "yes" if using SHLIBPATH_VAR=DIR during linking hardcodes DIR # into the resulting binary. hardcode_shlibpath_var=unsupported # Set to "yes" if building a shared library automatically hardcodes DIR # into the library and all subsequent libraries and executables linked # against it. hardcode_automatic=no # Set to yes if linker adds runtime paths of dependent libraries # to runtime path list. inherit_rpath=no # Whether libtool must link a program against all its dependency libraries. link_all_deplibs=unknown # Fix the shell variable $srcfile for the compiler. fix_srcfile_path="" # Set to "yes" if exported symbols are required. always_export_symbols=no # The commands to list exported symbols. export_symbols_cmds="\$NM \$libobjs \$convenience | \$global_symbol_pipe | \$SED 's/.* //' | sort | uniq > \$export_symbols" # Symbols that should not be listed in the preloaded symbols. exclude_expsyms="_GLOBAL_OFFSET_TABLE_|_GLOBAL__F[ID]_.*" # Symbols that must always be exported. include_expsyms="" # Commands necessary for linking programs (against libraries) with templates. prelink_cmds="" # Specify filename containing input files. file_list_spec="" # How to hardcode a shared library path into an executable. hardcode_action=immediate # The directories searched by this compiler when creating a shared library. compiler_lib_search_dirs="" # Dependencies to place before and after the objects being linked to # create a shared library. predep_objects="" postdep_objects="" predeps="" postdeps="" # The library search path used internally by the compiler when linking # a shared library. compiler_lib_search_path=""
net-mail/courier-imap-4.4.1 is now in portage
