Re: [Tracker] Delaying release to end of weekend while I investigate...

[Jamie McCracken <jamiemcc blueyonder co uk>]

Mikkel Kamstrup Erlandsen wrote:

> However cool Senna is I can't help but feel that inlining mysql is a BIG 
> deal... As a dev i personally don't mind, but I guess it might give you 
> trouble in the long run...
>  
>  - How big will the maintenance cost be?

zero unless I want to upgrade to a later version (which is unlikely 
unless there's a compelling reason to do so - 5.0.22 is more than stable 
enough)

The maintenance is much higher if I *dont* inline as I then have to 
tinker with stuff like the errmsg file which increases with each new 
version. mysql 5.1 is not guaranteed compatible with 5.0 so I avoid 
future problems too.

Also note the embedded mysql is not distributed outside debian. Fedora 
does not have it so they would have the pain of downloading 80mbs and 
compiling it with the correct compiler flags.

I currently inline libextractor and have not had any maintenance issues

>  - Is the 15MB you talk about acceptable? 15 MB is a lot!

Still less than Beagle and most other big gnome apps

>  - Could Senna be an optinal dep? Tracker falling back to ordinary 
> embedded mysql if it is not detected?

I will inline senna too. The sql index syntax can use either the built 
in mysql full text or the senna one so it can be a runtime config option 
rather than a compile time one.

>  - You *will* receive a lot of flak on this issue when you propose for 
> Gnome inclusion if mysql is inlined

Why?

If I dont then we lose the "just works" build. External dependencies are 
strongly discouraged to core gnome.

Anyway lets take evolution's berkeley DB as an example. This was a 25mb 
inline.


--
Mr Jamie McCracken
http://jamiemcc.livejournal.com/