From: Brian Evans <grknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] The future of virtual/mysql and virtual/libmysqlclient
Date: Tue, 13 Feb 2018 21:32:32 -0500 [thread overview]
Message-ID: <cbf267fa-3870-ca82-ea76-85950a89443b@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1063 bytes --]
I have a plan I would like some eyes on...
I want to gradually *BAN* the use of virtual/mysql and
virtual/libmysqlclient as dependencies.
To accomplish this, force dev-db/mysql-connector-c to be the only souce
of libmysqlclient.so.
Packages that choose to support libmariadb.so instead can include a
libmariadb USE to hook up to dev-db/mariadb-connector-c that will be
introduced (and they can live side-by-side). The motivation for this
could be licensing with libmariadb being LGPL instead of GPL. This is
similar to ffmpeg/libav, except the libraries can co-exist.
The current providers of virtual/mysql would get a new USE flag that is
MASKED for all users for the transition period and pull in the lib
package(s) when that USE is disabled.
virtual/mysql would become a server reference for USERS only. It would
be a QA warning violation to depend directly on virtual/mysql as it can
live anywhere.
virtual/libmysqlclient would be last-rite as it doesn't work as intended
That about sums it up.
Brian
MySQL team lead
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next reply other threads:[~2018-02-14 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 2:32 Brian Evans [this message]
2018-02-14 4:37 ` [gentoo-dev] The future of virtual/mysql and virtual/libmysqlclient Robin H. Johnson
2018-02-14 14:35 ` Francesco Riosa
2018-02-14 17:40 ` Brian Evans
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=cbf267fa-3870-ca82-ea76-85950a89443b@gentoo.org \
--to=grknight@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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