From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: MySQL - 5.6.19
Date: Fri, 15 Aug 2014 11:45:13 +0200
Message-ID: <1408095913.2114.118.camel@rice-oxley.tremer.info>
In-Reply-To: <1405678406.2679.1.camel@localhost>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2944353550209098011=="
List-Id: <development.lists.ipfire.org>

--===============2944353550209098011==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

please check if your branch still builds before you send patches. That's
the first thing to do. The second one is testing.

So mysql changed to cmake. Only the devil knows why.

You added cmake as a dependency (DEPS =3D) which is not necessary because
cmake is just a build dependency and not needed at runtime.

The configuration command worries me a bit more. Are the paths that were
passed to the configure command still honored with cmake? All files and
especially the databases need to remain in the same place to not break
existing installations.

Is it necessary to call mysql_install_db at build time?

What is the reason to remove the backup include file at the end?

How will the system migrate any pre-existing databases?

-Michael

On Fri, 2014-07-18 at 12:13 +0200, Sascha Kilian wrote:
> Hi there,
>=20
> i have committed a fix for my MySQL 5.6.19. The first version dont
> really worked in a fresh IPFire build
>=20
> https://bitbucket.org/tikira/ipfire-2.x/commits/02c5d5a5ee6d79c275c0edde51a=
21e2a99400b77
>=20
> best regards
>=20
> Sascha
>=20
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development


--===============2944353550209098011==--