I love the IDEA of Fedora, but I don't use it.

Fedora is Red Hat's experimental, community-based product.  It's bleeding 
edge.  That means stuff is often broken and changes in direction are not 
impossible.

This is not what I need, especially for a production server.

On Friday, March 8, 2013 6:57:18 PM UTC-5, LightDot wrote:
>
> I don't know in terms of user numbers but mysql is getting replaced with 
> mariadb in Fedora, which will have some impact.
>
> Current plan for Fedora 19 is this:
> - mariadb package will provide "mysql"
> - existing mysql package will be renamed to MySQL
> - mariadb and MySQL pacakges conflict, they can't be installed at the same 
> time.
>
> In others words, mariadb will act as a drop-in replacement for mysql. All 
> programs built against mysql libs will be rebuilt against the new "mysql" 
> libs, thus against mariadb. Everybody who installs "mysql" will in fact 
> install mariadb.
>
> There has been some debate about this mysql replacement and I'm expecting 
> further discussions, especially when Fedora 19 alpha and beta get released 
> and more users become aware of the change. I don't see any real changes for 
> the users though, at least not in the near future.
>
> Regards,
> Ales
>
> On Friday, March 8, 2013 9:39:38 PM UTC+1, Richard wrote:
>>
>> Thanks Cliff I wasn't about that issue, it's good to know that.
>>
>> I would be really curious to know if the MySQL user base had splitted 
>> since the MariaDB fork and what the proportion that stays with MySQL and 
>> now with MariaDB...
>>
>> Richard
>>
>>
>> On Fri, Mar 8, 2013 at 3:17 PM, Cliff Kachinske <[email protected]> wrote:
>>
>>> @Richard
>>>
>>> Yeah, I know.  But what about documentation?
>>>
>>> The MySQL code itself is free open source, but Oracle owns the copyright 
>>> on the MySQL documentation.
>>>
>>> So as the MariaDB fork adds features, the MySQL documentation becomes 
>>> more and more inaccurate.  At some point there will have to be a full 
>>> rewrite of the MariaDB docs.  Just seems too messy.
>>>
>>>
>>> On Friday, March 8, 2013 8:44:52 AM UTC-5, Richard wrote:
>>>
>>>> @Cliff MariaDB!!
>>>>
>>>> :)
>>>>
>>>> Richard
>>>>
>>>>
>>>> On Fri, Mar 8, 2013 at 7:36 AM, Cliff Kachinske <[email protected]>wrote:
>>>>
>>>>> It's not just the legal aspect.
>>>>>
>>>>> After seeing how poorly Oracle supported OpenOffice, I would be 
>>>>> concerned about their future support for MySQL as well.
>>>>>
>>>>>
>>>>> On Friday, March 8, 2013 4:43:06 AM UTC-5, Niphlod wrote:
>>>>>>
>>>>>> This is going nuts. He was fine until now with SQLite, either one of 
>>>>>> mysql or postgres will do fine, with a total preference on postgres if 
>>>>>> he 
>>>>>> doesn't want to employ a legal office to know if he can use mysql or not.
>>>>>>
>>>>>> PS: the day I'm going to choose mysql over postgres for the combined 
>>>>>> requirement of having:
>>>>>> - a nice syntax to expose an autoincrementing field
>>>>>> - is able to accomodate 8M rows with 3 bytes instead of 4 (I'll never 
>>>>>> consider a tiny or a smallint as an autoincrement-eligible field) 
>>>>>> it's the day I'll stop working on databases.
>>>>>>
>>>>>>  -- 
>>>>>  
>>>>> --- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "web2py-users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to web2py+un...@**googlegroups.com.
>>>>>
>>>>> For more options, visit 
>>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>>> .
>>>>>  
>>>>>  
>>>>>
>>>>
>>>>  -- 
>>>  
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "web2py-users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>
>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to