Jared K. Smith wrote:
> Yes, we heard you the first three times you said that -- and it's
> still not happening, at least for now.
Each of the three times pointed out a new showstopper-level problem with
having the 2 forks coexist. It's sad that no amount of technical
impossibility is convincing
On Wed, Mar 13, 2013 at 5:27 PM, Kevin Kofler wrote:
> The best would be to just remove MySQL from the distribution. Sorry.
Yes, we heard you the first three times you said that -- and it's
still not happening, at least for now. You're not doing yourself any
favors by repeating yourself, especi
Norvald H. Ryeng wrote:
> The best would be to make the packages non-conflicting, either completely
> separate or using alternatives to set a default.
The best would be to just remove MySQL from the distribution. Sorry.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
ht
On Tue, 12 Mar 2013 17:59:50 +0100, Honza Horak wrote:
On 03/06/2013 02:44 PM, Miloslav Trmač wrote:
On Wed, Mar 6, 2013 at 2:35 PM, Norvald H. Ryeng
wrote:
In practice, this means that it will be almost impossible to install
MySQL
in Fedora. The recipe in the feature page [1] requires the
On 03/06/2013 02:44 PM, Miloslav Trmač wrote:
On Wed, Mar 6, 2013 at 2:35 PM, Norvald H. Ryeng
wrote:
In practice, this means that it will be almost impossible to install MySQL
in Fedora. The recipe in the feature page [1] requires the user to
1. edit yum.conf to set excludes=mariadb* and obso
Am 11.03.2013 19:12, schrieb Honza Horak:
> On 03/09/2013 07:20 PM, Reindl Harald wrote:
>> and why in the world is this not solved more pragmatically?
>>
>> my conslusion is
>> * MariaDB will replace mysql as default
>> * any package will be linked against mariadb
>> * Oracle MySQL should only p
Miloslav Trmač wrote:
> The FESCo decision from the minutes was:
>> feature owners are asked to make it possible to install the MySQL
>> stand-alone server (only)
> so dependencies on the client libraries are not a concern; Fedora
> packages are expected to use the MariaDB client libraries.
In oth
Am 09.03.2013 19:43, schrieb Kevin Fenzi:
> To be clear, this was me, in my role as moderator of this list.
>
> I just don't think every subscriber on this list wants a copy of your
> mariadb spec when interested people can just follow a link to it
maybe you have a bad day
431 lines plaintext
On Sat, 09 Mar 2013 19:20:08 +0100
Reindl Harald wrote:
> > "When I asked you to repost with just a link, I didn't mean also
> > attach the orig email with the 20k spec file that was the reason the
> > mail was too long in the first place."
>
> maybe you should make clearer what you want if you
On 03/06/2013 08:44 AM, Miloslav Trmač wrote:
File conflicts within the server packages might still be a concern, I
don't know. Per the decision quoted above, FESCo would prefer the
maintainers of the two servers to agree on a solution.
If the maintainers don't reach a solution or if one of th
On Wed, Mar 6, 2013 at 2:35 PM, Norvald H. Ryeng
wrote:
> In practice, this means that it will be almost impossible to install MySQL
> in Fedora. The recipe in the feature page [1] requires the user to
>
> 1. edit yum.conf to set excludes=mariadb* and obsoletes=0,
> 2. run yum shell to replace the
On Tue, 05 Mar 2013 19:14:25 +0100, Honza Horak wrote:
On 03/05/2013 11:07 AM, Norvald H. Ryeng wrote:
On Thu, 14 Feb 2013 16:17:00 +0100, Tom Lane wrote:
The way this worked in the past (and still does on RHEL and some other
distros) is that MySQL AB provided RPMs named "MySQL", "MySQL-serv
On 5. 3. 2013 at 19:14:25, Honza Horak wrote:
> On 03/05/2013 11:07 AM, Norvald H. Ryeng wrote:
> > On Thu, 14 Feb 2013 16:17:00 +0100, Tom Lane wrote:
> >> The way this worked in the past (and still does on RHEL and some other
> >> distros) is that MySQL AB provided RPMs named "MySQL", "MySQL-ser
13 matches
Mail list logo
