| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 7/17/2015 2:04 PM, NP-Hardass wrote: |
| 5 |
> On 07/17/2015 01:56 PM, Brian Evans wrote: |
| 6 |
>> Title: MySQL client libraries and server packaging changes |
| 7 |
>> Author: Brian Evans <grknight@g.o> Content-Type: |
| 8 |
>> text/plain Posted: 2015-07-17 Revision: 1 News-Item-Format: 1.0 |
| 9 |
>> Display-If-Installed: virtual/mysql |
| 10 |
> |
| 11 |
>> The future of the mysql packages is changing. |
| 12 |
> |
| 13 |
>> First off, a new virtual is being introduced, |
| 14 |
>> virtual/libmysqlclient. virtual/mysql will represent the server |
| 15 |
>> and tools while virtual/libmysqlclient will represent the shared |
| 16 |
>> and static libraries. |
| 17 |
> |
| 18 |
>> Developers and ebuild writers should reference |
| 19 |
>> virtual/libmysqlclient when linking against the libraries as the |
| 20 |
>> package will keep the subslot the same as the soversion for easy |
| 21 |
>> rebuilds. This is getting more difficult in the current virtual |
| 22 |
>> situation as MySQL and MariaDB start to diverge versions and |
| 23 |
>> features. The old method could force users to mask new versions |
| 24 |
>> or delay the posting of one server package which advances the |
| 25 |
>> soversion until the others catch up. |
| 26 |
> |
| 27 |
>> As for the server packages themselves, the minimal USE is being |
| 28 |
>> replaced. The new USE flags are client-libs, +server, and +tools. |
| 29 |
>> The server and tools flags are on by default to signify the |
| 30 |
>> primary purpose of those builds. |
| 31 |
> |
| 32 |
>> The primary provider for libraries will be a new package |
| 33 |
>> dev-db/mysql-connector-c. A tinderbox run did not turn up any |
| 34 |
>> issues, but packagers are permitted to block any provider of |
| 35 |
>> virtual/libmysqlclient that does not work correctly. A comment |
| 36 |
>> in the ebuild would be helpful to track this. The server |
| 37 |
>> packages can still provide libraries if the client-libs USE is |
| 38 |
>> enabled. |
| 39 |
> |
| 40 |
> |
| 41 |
> It's my understanding that news items are geared to end users, |
| 42 |
> however, this may be incorrect. Assuming that is the case, apart |
| 43 |
> from notifying the users about the USE flag changes, the bulk of |
| 44 |
> this news item is geared toward devs and package maintainers. As |
| 45 |
> such, I feel like the user relevant content might go unnoticed as |
| 46 |
> they skim and see it is primarily maintainer related. |
| 47 |
|
| 48 |
Unfortunately, I am a terrible writer and just spill thoughts out. |
| 49 |
|
| 50 |
The users might still have to know about setting client-libs or using |
| 51 |
the new virtual if they set the minimal flags in the past. Will have |
| 52 |
to think on that. |
| 53 |
|
| 54 |
Brian |
| 55 |
|
| 56 |
-----BEGIN PGP SIGNATURE----- |
| 57 |
Version: GnuPG v2.0.17 (MingW32) |
| 58 |
|
| 59 |
iQIcBAEBAgAGBQJVqUw2AAoJENH3ge/59KO2LYEQANdHnvjYBTTB5NLmvoFUBmF+ |
| 60 |
ekZEeoEsfIcSSQ9JISlNoZy05AKFqK1C+zd4+OnS+uVcaSId/MdEAXDD5ahtE8Je |
| 61 |
F9EuTaT3xAFaR2RG/OxiW8iyqV+2iX2126h3YrkHC+4zRQyf8S7dYaQqUzYtsv/H |
| 62 |
GAkyFD+F5f3MOXYsEsFVPvSn5BKQ5AmTnAGUpsr/RwEE9YaXVc1lyldPtPPMk527 |
| 63 |
Pc4wiZWRUBRxAe0NKuzFr0DM/7nOqBDVbsdsD9YtSMsLlvNu0qQtfActY0mgl4FU |
| 64 |
CZSfRhyvhzwKD4i9Bf/BODbOc8RgThVV0Vcpl/XxHzyPNxCCALDYAoNFEvfnV251 |
| 65 |
Fj8oGrmheVrM/DGqV0uKL+1jS2zrYQiTk5GlQut8KN7FGIz3//DOCnXt3BepdrIr |
| 66 |
AdgUdThc3Tz09PrGipya8C3T89tGQ7Q1H/8bI2v9ZvLjF5f81TG+s1KtSk2TRobd |
| 67 |
GXaplNHSjzLU98SPXshXddG0e7fWbjDXZP0J0k+PdRX0gDokN+YjWGiDAjHPj5n7 |
| 68 |
aLpWLRw3qdb/895Cgw1J5LyWSQ0W8dwa2/7c1N+ZP6eignPy/1b2p+yNORkjE5Y4 |
| 69 |
tmoJZYLbHihjoHPr6EFIB5UCxPvy7NqFQeU+iKTr5YNVblkhZqX1XrlR8JijiiRk |
| 70 |
KReddKPprFtanFiUmkFQ |
| 71 |
=EuG2 |
| 72 |
-----END PGP SIGNATURE----- |
Archives