kmail cannot send email : reason identified (?)

[Nicolas Pavillon]

Hello, 

I am indeed the culprit for this one. However, there is a little bit more to it than the fact that I could not find anything using it (missing kmail, obviously), thus commenting it out. 

All kde Portfiles had a conflict between their GPL-2 license and the openssl one, on which they depend. This was preventing the distribution of all ports as binary, forcing users
to build all ports from source, requiring a massive amount of time, and adding several bug tickets due to several issues with specific configurations. 
I then started looking into each port, in order to determine if they were really linking with openssl or not. For most of them, they did not, so that it was possible to bypass the 
license conflict to enable binary distribution. 

Then, for kdepimlibs, the module io-slave links to openssl for what I saw in the past, which was preventing distribution at a rather low level (several ports then depends on 
kdepimlibs4). Since I could not find any port using this module, I deactivated it in order to enable binary distribution. 

Then, if it breaks other ports, this becomes of course another story, and the fact of commenting out the module does not make much sense. However, I would be keen on 
finding a way which does not break binary distribution.

Cheers, 

Nicolas


On Mar23, 2014, at 3:09, René J.V. Bertin <rjvbertin at gmail.com> wrote:

> 
> On Mar 22, 2014, at 16:54, Brandon Allbery wrote:
> 
>> Any idea what this was commented out?
>> Is that a patch applied only to make KMail run on MacPorts or is that coming from KDE?
> 
> The comment in the Portfile (from Nicos) states that "we don't need it" ...
> 
> Anyway, I just rebuilt the port from sources after commenting out the patch entry as well as the MAILTRANSPORT_INPROCESS_SMTP off switch. In other words, the port should have been build as much stock as possible. No luck, sadly, but I guess I'll have to try rebuilding the kdepim runtime too.
> 
>> KDE on OS X already starts plenty of daemons (notably kdeinit). While you're "supposed" to do stuff through launchd, it's not absolutely mandatory, can't be enforced, and KDE would be rather difficult to get working at all if you couldn't.
> 
> All (or most) those daemons are started through DBus, and that in itself seems to work.
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users