On 2014-07-02 21:14, Mike Gabriel wrote:
On Mi 02 Jul 2014 14:09:10 CEST, Sune Vuorela wrote:
I want to ensure that neither of us gets to debug weird crashes if
both
libraries are loaded into the same application.
@Sandro/Kolabsys: to me it feels as if Sune suggestions should be
implemented
Hi Sandro, hi Sune,
@Sune: thanks for being supportive on this issue!!!
On Mi 02 Jul 2014 14:09:10 CEST, Sune Vuorela wrote:
On Wednesday 02 July 2014 13:36:52 Sandro Knauß wrote:
[...]
[...]
I want to ensure that neither of us gets to debug weird crashes if both
libraries are loaded
On Wednesday 02 July 2014 13:36:52 Sandro Knauß wrote:
> Hey,
>
> I have some comments/questions:
> > 1) libcalendaring-* doesn't have a single symbol in common with kdepimlibs
> > *and*
> why is that needed? all libs are named differently, have a different version
> and the headers will lay in /
Hey,
I have some comments/questions:
> 1) libcalendaring-* doesn't have a single symbol in common with kdepimlibs
> *and*
why is that needed? all libs are named differently, have a different version
and the headers will lay in /usr/include/calendaring/ ->I don't see the
point, why compile two
Hi Diane,
On So 29 Jun 2014 20:12:23 CEST, Diane Trout wrote:
I mentioned the libcalendaring thing in #debian-qt-kde, Sune Vuorela
(svuorela) listed these as his requirements for libcalendaring getting into
Debian.
1) libcalendaring-* doesn't have a single symbol in common with kdepimlibs
*an
5 matches
Mail list logo
