[calligra] /: Move core parts of KexiDB lib to libcalligradb

[C. Boemann]

On Friday 13 July 2012 10:11:20 Boudewijn Rempt wrote:
> On Friday 13 July 2012 Jul, C. Boemann wrote:
> > On Friday 13 July 2012 08:45:13 Cyrille Berger Skott wrote:
> > > On Friday 13 Jul 2012, you wrote:
> > > > Flexibility is a +1, but one -1 (besides adding further complexity to
> > > > cmake files) is that these build profiles should only be used for
> > > > custom builds. We don't want stripped-down Word in the popular
> > > > distros, for example, not being able to handle the Biblio feature.
> > > 
> > > You really don't have to worry about distributions, packagers will
> > > package with every optional dependency as possible, and as long as
> > > they are listed at the end of the configuration step, they will notice
> > > them and include them. This is why we often get the complain that
> > > Calligra installation is bloated. Personnaly, I think it is ok.
> > > 
> > > However I thought we were in agreement that we wanted to make it
> > > possible to create very lightweight custom build of calligra with as
> > > few dependencies as possible.
> > > 
> > > In any case, new hard dependencies need to be discussed and announced
> > > on the mailing list in advance.
> > 
> > uhm there was a review request for about a week
> 
> Yeah, I saw that request. But that's not the same same as writing a mail to
> the mailing list announcing extra dependencies. I saw the request, but I
> was blindsided by it as well.
I'm not sure I like it if we make it even easier to ignore review requests, 
but okay the request in question should probably have called more attention to 
the new dependency.

It's not like review requests are not sent to the mailing list.