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 [thread overview]
Message-ID: <1408095913.2114.118.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <1405678406.2679.1.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
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 =) 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,
>
> i have committed a fix for my MySQL 5.6.19. The first version dont
> really worked in a fresh IPFire build
>
> https://bitbucket.org/tikira/ipfire-2.x/commits/02c5d5a5ee6d79c275c0edde51a21e2a99400b77
>
> best regards
>
> Sascha
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
prev parent reply other threads:[~2014-08-15 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 10:13 Sascha Kilian
2014-08-15 9:45 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1408095913.2114.118.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox