ebuild submission for mailsync http://mailsync.sourceforge.net for keyword I set "x86" since there isn't a whole lot that could go wrong with this... also my first ebuild so please look over thoroughly... it may compile on other arch, but I've no way to test it, and from the README: "I've only compiled mailsync-4 on Linux and on SGI-Irix 6.5. With a little coaxing, though, it should compile on any unix-like system on which c-client compiles. On a non-unix-like system, you may have to come up with alternatives to a few functions like stat() and getenv()." please note any errors I may have made for my future reference Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 33000 [details] proposed mailsync-5.1.2.ebuild
Things you might want to fix: * Use mirror://sourceforge/${PN}/${P}.tar.gz for SRC_URI. * Use econf rather than ./configure if possible. Otherwise, include a comment saying why econf is no good. * GPL-1? Really? * Surely you need to call emake / make?
Created attachment 33002 [details] mailsync-5.1.2.ebuild incoporated suggested fixes
Created attachment 33545 [details] mailsync-5.1.2.ebuild here is an even more cleaned up ebuild the only problem(s) left that prevent this from being included are handling of optional support for openssl/krb5/pam/c-client from `./configure --help`: --with-openssl=prefix enable use of OpenSSL --with-krb5=prefix enable use of kerberos --with-pam enable use of PAM --with-c-client=path enable use of c-client
Created attachment 33546 [details, diff] 5.1.2-gcc34.patch patch to compile with gcc-3.4 ... should be save for all gcc versions though
Created attachment 33580 [details] mailsync-5.1.2.ebuild thanks for the help, patch applies & compiles cleanly on gcc 3.3.3-r6 tested this ebuild, enables use options, works fine here
Created attachment 37863 [details] mailsync 5.2.1 ebuild I'm one of those involved in mailsync development and I have recently installed gentoo with all the logical consequences. I've prepared the ebuild and what I was about to submit I found your effort in this direction. I believe the new mailsync version does not require gcc 3.4 patch. And actually, mailsync does not require USE flags, since the usage of libraries depends on c-client configuration and specifying inconsistent with c-client installation USEs will get us nowhere. I realize that 'enable use' lines in ./configure --help output may sound misleading, though.
I have installed heimdal in /usr/heimdal. So I went to check how this program compiles against heimdal of if it requires mit-krb5. I ran configure without any arguments and got: checking for main in -lcrypto... yes checking for openssl/ssl.h... found in /usr/include checking for krb5-config... found /usr/bin/krb5-config checking for pam library... found in /usr/lib checking for pam headers... found in /usr/include Hmm, where did I get /usr/bin/krb5-config I thought ... # emerge -s krb5 Searching... [ Results for search key : krb5 ] [ Applications found : 2 ] * app-crypt/mit-krb5 Latest version available: 1.4.1-r2 Latest version installed: [ Not Installed ] Size of downloaded files: 6,513 kB Homepage: http://web.mit.edu/kerberos/www/ Description: MIT Kerberos V License: as-is * sys-auth/pam_krb5 Latest version available: 20030601-r1 Latest version installed: [ Not Installed ] Size of downloaded files: 314 kB Homepage: http://pam-krb5.sourceforge.net/ Description: Pam module for MIT Kerberos V and Heimdal License: LGPL-2 # equery belongs /usr/bin/krb5-config [ Searching for file(s) /usr/bin/krb5-config in *... ] app-crypt/heimdal-0.6.5 (/usr/bin/krb5-config) # OK, now I know, I have heimdal-0.6.5 from Gentoo as a bonus and in /usr where it really sucks as it is causing just problems (should be in /usr/heimdal). So, I got rid of heimdal-0.9.6 from /usr and continued: # ./configure --with-krb5=/usr/heimdal [cut] checking for libssl... found in /usr/lib checking for main in -lssl... yes checking for main in -lcrypto... yes checking for openssl/ssl.h... found in /usr/include checking for krb5-config... found /usr/heimdal/bin/krb5-config checking for pam library... found in /usr/lib checking for pam headers... found in /usr/include checking if pam test program compiles... yes checking for c-client.h... found in /usr/include/imap checking for c-client library... found /usr/lib/libc-client.a checking whether c-client built with kerberos gssapi support... no checking if kerberos is required and available for linking against c-client... not required checking whether c-client requires ssl linkage... yes checking if simple c-client program compiles without pam support... no checking if we've seen pam somewhere around... yes checking if adding pam helps... yes checking if c-client works without -fno-operator-names in c++... no [cut] if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/imap -g -O2 -MT msgstring.o -MD -MP -MF ".deps/msgstring.Tpo" \ -c -o msgstring.o `test -f 'msgstring.c' || echo './'`msgstring.c; \ then mv -f ".deps/msgstring.Tpo" ".deps/msgstring.Po"; \ else rm -f ".deps/msgstring.Tpo"; exit 1; \ fi g++ -fno-operator-names -g -O2 -o mailsync mailsync_main.o commandline.o configuration.o types.o mail_handling.o c-client_callbacks.o utils.o store.o channel.o msgid.o msgstring.o /usr/lib/libc-client.a -L/usr/lib -lssl -lcrypto -L/usr/lib -lpam -lcrypt /usr/lib/libc-client.a(osdep.o): In function `ssl_onceonlyinit': osdep.c:(.text+0xac43): warning: the use of `tmpnam' is dangerous, better use `mkstemp' make[2]: Leaving directory `/scratch/mailsync-5.2.1/src' make[2]: Entering directory `/scratch/mailsync-5.2.1' make[2]: Leaving directory `/scratch/mailsync-5.2.1' make[1]: Leaving directory `/scratch/mailsync-5.2.1' ribosome mailsync-5.2.1 # Do you see any kerberos related libraries there? I do not! config.status has: s,@OPENSSL_INCLUDES@,-I/usr/include,;t t s,@OPENSSL_LDFLAGS@,-L/usr/lib,;t t s,@OPENSSL_LIBS@, -lssl -lcrypto,;t t s,@HAVE_OPENSSL_TRUE@,,;t t s,@HAVE_OPENSSL_FALSE@,#,;t t s,@KRB5_CONFIG@,/usr/heimdal/bin/krb5-config,;t t s,@KRB5_CFLAGS@,-I/usr/heimdal/include ,;t t s,@KRB5_LDFLAGS@,-L/usr/heimdal/lib -lkrb5 -lasn1 -lcom_err -lcrypto -lroken -lcrypt -ldb -lresolv -pthread,;t t s,@HAVE_KRB5_TRUE@,,;t t s,@HAVE_KRB5_FALSE@,#,;t t s,@KRB5_GSSAPI_CFLAGS@,-I/usr/heimdal/include ,;t t s,@KRB5_GSSAPI_LIBS@,-L/usr/heimdal/lib -lgssapi -lkrb5 -lasn1 -lcom_err -lcrypto -lroken -lcrypt -ldb -lresolv -pthread,;t t s,@HAVE_KRB5_GSSAPI_TRUE@,,;t t s,@HAVE_KRB5_GSSAPI_FALSE@,#,;t t There are no other lines propagating KRB stuff downstream. grepping for krb yields only docfiles, no source files. I think, kerberos support was removed. Read mailsync-5.2.1/debian/changelog. Briefly, just zap the kerberos related USE/RDEPEND/DEPEND flags, it is useless here. The kerberos detection stuff is the only kerberos support at the moment left in mailsync.
In cvs, thanks all for input and ebuilds.
