Hi all, this is my first mail here, please correct if is not the right place to post this kind of informations. The current port of postfix doesn't work well, so I did some work trying to make it ok: Attached are: - a simple patch to postfix-script so it can correctly recognise folders permissions - a patch to the portfile which: * add cyrus support (this must be done explicitely in 2.3.X) * try to compile postfix against _system_ openssl and _macports'_ sasl2 * bump postfix version to 2.3.4 There's one unresolved issue, no matter if I explicitly compile it against system or macports version of openssl, I have this warning: ------ postfix/smtp[24927]: warning: run-time library vs. compile-time header version mismatch: OpenSSL 0.9.8 may not be compatible with OpenSSL 0.9.7 ------ Which means it compiles against system version of openssl and uses macports' one at run time. As a result I can't start a tls connection with any mailserver. After installation 2 files must be deleted (I don't know which is the best way to do this in the Portfile): /opt/local/var//spool/postfix/maildrop/.turd_postfix /opt/local/var//spool/postfix/public/.turd_postfix Please let me know what do you think about this, and forgive me if something is wrong because this is my first attempt to modify a port. Gufo -- ,___, If you're not part of the solution, (9v9) you're part of the precipitate (_^((\ My site: http://gufo.dontexist.org/ -^-"-"-\\-^-- Gpg Key at: http://gufo.dontexist.org/db.asc
On Sep 28, 2006, at 12:25 PM, Gufo wrote:
this is my first mail here, please correct if is not the right place to post this kind of informations.
The best way to get this to the right person would be to open a bug in trac, assign it to the port maintainer, and attach your patches.
The current port of postfix doesn't work well, so I did some work trying to make it ok:
Attached are: - a simple patch to postfix-script so it can correctly recognise folders permissions - a patch to the portfile which: * add cyrus support (this must be done explicitely in 2.3.X) * try to compile postfix against _system_ openssl and _macports'_ sasl2
We try to use macports provided libraries whenever possible. (see http://trac.macports.org/projects/macports/wiki/FAQ - "Why is MacPorts using its own libraries?")
* bump postfix version to 2.3.4
There's one unresolved issue, no matter if I explicitly compile it against system or macports version of openssl, I have this warning:
------ postfix/smtp[24927]: warning: run-time library vs. compile-time header version mismatch: OpenSSL 0.9.8 may not be compatible with OpenSSL 0.9.7 ------
Which means it compiles against system version of openssl and uses macports' one at run time.
It means it found one version of the openssl headers and is linked to a different version of the library ... that's bad and is probably why you are having tls issues.
As a result I can't start a tls connection with any mailserver.
After installation 2 files must be deleted (I don't know which is the best way to do this in the Portfile):
/opt/local/var//spool/postfix/maildrop/.turd_postfix /opt/local/var//spool/postfix/public/.turd_postfix
You can't really delete those files on install, but they are an old holdover from before we had destroot.keepdirs , so you can probably change the portfile to no longer generate them. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
"Daniel J. Luke" <dluke@geeklair.net> writes:
After installation 2 files must be deleted (I don't know which is the best way to do this in the Portfile):
/opt/local/var//spool/postfix/maildrop/.turd_postfix /opt/local/var//spool/postfix/public/.turd_postfix
You can't really delete those files on install, but they are an old holdover from before we had destroot.keepdirs , so you can probably change the portfile to no longer generate them.
I don't understand. destroot.keepdirs generates those files as well. Wouldn't deleting them in the post-activate phase still adhere to our guidelines? I hope so because I did that with one port of mine. I wish there were a better way to create empty directories. Mark
On Sep 28, 2006, at 3:01 PM, Mark Duling wrote:
You can't really delete those files on install, but they are an old holdover from before we had destroot.keepdirs , so you can probably change the portfile to no longer generate them.
I don't understand. destroot.keepdirs generates those files as well.
I guess you're right, I thought that destroot.keepdirs preserved the directories without creating those files, but I was wrong.
Wouldn't deleting them in the post-activate phase still adhere to our guidelines? I hope so because I did that with one port of mine. I wish there were a better way to create empty directories.
post-activate doesn't run in direct mode. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On Sep 28, 2006, at 12:01 PM, Mark Duling wrote:
"Daniel J. Luke" <dluke@geeklair.net> writes:
After installation 2 files must be deleted (I don't know which is the best way to do this in the Portfile):
/opt/local/var//spool/postfix/maildrop/.turd_postfix /opt/local/var//spool/postfix/public/.turd_postfix
You can't really delete those files on install, but they are an old holdover from before we had destroot.keepdirs , so you can probably change the portfile to no longer generate them.
I don't understand. destroot.keepdirs generates those files as well. Wouldn't deleting them in the post-activate phase still adhere to our guidelines? I hope so because I did that with one port of mine. I wish there were a better way to create empty directories.
Yeah, unfortunately those files are actually created by destroot.keepdirs. I think because at various places empty directories are otherwise nuked, which probably isn't advisable. Patches are welcome. James
Hello Gufo! I'm replying to your original mail a little late, since I'm just catching up with mail here, so I can only hope my comments are still applicable! On Sep 28, 2006, at 12:25 PM, Gufo wrote:
Hi all, this is my first mail here, please correct if is not the right place to post this kind of informations.
For these kinds of questions, this is the correct list to post to, yes. ---snip---
There's one unresolved issue, no matter if I explicitly compile it against system or macports version of openssl, I have this warning:
------ postfix/smtp[24927]: warning: run-time library vs. compile-time header version mismatch: OpenSSL 0.9.8 may not be compatible with OpenSSL 0.9.7 ------
Which means it compiles against system version of openssl and uses macports' one at run time. As a result I can't start a tls connection with any mailserver.
Proper use of CFLAGS, CPPFLAGS and LDFLAGS environment variables usually helps Makefiles locate appropriate header files and corresponding libraries, so I'd play with these in the Portfile's "configure.env" and "build.env" variables until the build is considered satisfactory. If no combination of them achieves that goal, then I'm afraid a patch against some Makefile would have to be written and listed in the Portfile's "patchfiles" variable.
After installation 2 files must be deleted (I don't know which is the best way to do this in the Portfile):
/opt/local/var//spool/postfix/maildrop/.turd_postfix /opt/local/var//spool/postfix/public/.turd_postfix
.turd files are created by MacPorts through the values of the "destrook.keepdirs" variable to keep our post-destroot phase from deleting at-installation-time empty directories that the port might need once installed and running. Why do you need to remove them? If the directories are indeed empty and unnecessary, then look for stray "destroot.keepdirs" declarations in the Portfile and remove those, not the .turd files manually (at least that's my advice). Regards,... -jmpp
participants (5)
-
Daniel J. Luke
-
Gufo
-
James Berry
-
Juan Manuel Palacios
-
Mark Duling