mysql: propagate common dependencies to toplevel config
authorPeter Korsgaard <peter@korsgaard.com>
Mon, 9 Jan 2017 10:56:54 +0000 (11:56 +0100)
committerPeter Korsgaard <peter@korsgaard.com>
Mon, 9 Jan 2017 12:44:12 +0000 (13:44 +0100)
commit8b6dad32a25274cb9fe56b09da356ade47cb83f9
tree08f81e77883187d17ba8c2a8d689812d4cb9310e
parent43d24b533496d7a1d8bf949db750e20d68b79660
mysql: propagate common dependencies to toplevel config

Commit 3d707d2b (mysql: rename package to oracle-mysql, make a virtual
package) introduced a user selectable virtual BR2_PACKAGE_MYSQL package, but
didn't propagate the (common) dependencies of the two variants to it, so the
virtual package can now be selected even though neither of the variants are
available.

As several packages enable mysql support when BR2_PACKAGE_MYSQL is selected,
this causes a number of autobuilder issues:

http://autobuild.buildroot.net/results/7fe/7fe0d0a3e7ed0430852dc42b718dd037557207e8/
http://autobuild.buildroot.net/results/cc4/cc4c2d936f3e1ba6c0a9782b2218de54a4ff75d2/

Fix it by propagating the common dependencies of the two variants to the
virtual package to ensure it cannot be enabled unless at least one of them
are available.

Also move the toolchain comment outside the conditional so it is visible
when mysql isn't available.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
package/mysql/Config.in