On 1/6/08, Guido Soranzio < guido.soranzio@gmail.com> wrote:

On Jan 6, 2008, at 8:24 PM, Tabitha McNerney wrote:

> I just had an idea. Why not use Apple's libssl.so that comes with
> Leopard Server


Because the goal of the MacPorts project is the contrary of that:
we should mess with the sources provided by third parties, not with
the binaries distributed by Apple!

Guido, I am with you and agree with you. MacPorts should have the goal of being as independent as possible. And that reminds me then that I should take a closer look to see why the kaffe port will not build on Leopard, too (rather than using Apple Leopard Server's Tomcat, since I want to build Tomcat from MacPorts and it depends on Kaffe).
 

I have tried to apply the rough workaround I suggested you; these
are the simple steps I followed:


* extract the sources of Apache with "sudo port extract apache2"

Guido, this is fascinating! I was not aware of the command-line tool named "extract". I don't see it in my PATH on either my Tiger Server or Leopard Server system. I also don't see "extract" as a MacPort as in:

$ port info extract
Error: Port extract not found

Could you point me (and the MacPorts mailing list) to where we can find the extract command-line tool? Thank you!