Hello!
I have now implemented this. Please review latest git commits
(http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git), in
particular:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=7a3739d903e2e2584660544c5ab2545f7f9d4447
http://anonscm.debian.org/cgit/pkg-mysql/m
Arnaud: any chance of progress for this one?
Hi,
> 2015-02-27 8:31 GMT+02:00 Arnaud Fontaine :
>> Great. I don't think it's an urgent task but I will start splitting up
>> the package when I have some time if that's ok with you?
>
> Do you think you might have some time now..? :)
I'm really sorry, I don't have much time for Debian ATM as
Hello!
2015-02-27 8:31 GMT+02:00 Arnaud Fontaine :
> Great. I don't think it's an urgent task but I will start splitting up
> the package when I have some time if that's ok with you?
Do you think you might have some time now..? :)
Otto Kekäläinen writes:
> 2015-02-26 10:36 GMT+02:00 Arnaud Fontaine :
>>> I'd vote for this. Let's put at least all the big plugins in their own
>>> packages. The main mariadb-server-10.0 could include only the plugins
>>> that are loaded by default or that are just really small.
>>
>> Actually,
2015-02-26 10:36 GMT+02:00 Arnaud Fontaine :
>> I'd vote for this. Let's put at least all the big plugins in their own
>> packages. The main mariadb-server-10.0 could include only the plugins
>> that are loaded by default or that are just really small.
>
> Actually, none of these plugins are ena
Hi,
Otto Kekäläinen writes:
> I'd vote for this. Let's put at least all the big plugins in their own
> packages. The main mariadb-server-10.0 could include only the plugins
> that are loaded by default or that are just really small.
Actually, none of these plugins are enabled by default AFA
2015-02-10 8:45 GMT+02:00 Arnaud Fontaine :
> 1. Create one package per plugin as you suggested, but this would
> create many (some of them really small) packages though. Or perhaps
> one package containing several plugins, because some of them, such
> as query_cache_info, ar
Hi Otto,
Otto Kekäläinen writes:
> After thinking about it for a while, I am starting to think that the
> best policy would be to _not_ load bundled plugins by default if they
> are not compulsory for the server to run. It is better to keep the
> server lean and sleek, and let the user activate
After thinking about it for a while, I am starting to think that the
best policy would be to _not_ load bundled plugins by default if they
are not compulsory for the server to run. It is better to keep the
server lean and sleek, and let the user activate extra plugins if they
need them.
We could h
10 matches
Mail list logo
