[Buildroot] [PATCH 1/1] package/mysql: change default implementation to mariadb
Peter Korsgaard
peter at korsgaard.com
Sun Mar 3 17:55:16 UTC 2024
>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot at buildroot.org> writes:
> On 02/03/2024 15:37, Yann E. MORIN wrote:
>> Julien, All,
>> On 2024-03-01 22:45 +0100, Julien Olivain spake thusly:
>>> On 01/03/2024 09:24, Peter Korsgaard wrote:
>>>>>>>>> "Julien" == Julien Olivain <ju.o at free.fr> writes:
>>>> > The mysql package is a virtual package with two implementations:
>>>> > oracle-mysql (the initial project), and mariadb (the fork of mysql).
>>>> > This virtual package was introduced in commit [1] (2016).
>>>> > The last version bump of oracle-mysql was in commit [2] (2014). This
>>>> > mysql version 5.1.73 dates from 2013 [3].
> There's one reason to prefer oracle-mysql: mariadb (server) is almost
> twice as big.
OK, but are there a lot of use cases where you need a full blown SQL
server but don't have a lot of space for the code or database?
>>> My initial intent was to raise the attention on this decade old package,
>>> with quite a few CVEs associated to it ;)
>> "Quite a few" is probably the best understatement of the year (and
>> it's
>> only March!). ;-)
>> So I'd side with Peter here: drop it, and then drop the virtual
>> package.
> Agreed to that.
> Anyway, I think mysql and mariadb are less and less drop-in
> replacements, so the virtual package is
> If really needed, I think mariadb has a few large subparts that can
> (optionally) be dropped, so it should be possible to reduce the
> footprint. If someone bothers to work on that, of course :-)
We are really close to 2024.02 release, but I'll try to cook up a patch
for dropping oracle-mysql / the virtual package now.
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list