| 1 |
On 11/02/2015 06:48 PM, Michael Orlitzky wrote: |
| 2 |
> In the dev-lang/php ebuilds, we currently have: |
| 3 |
> |
| 4 |
|
| 5 |
.. |
| 6 |
|
| 7 |
> |
| 8 |
> Is there a way to say "give me any 4.x or 5.x slot"? |
| 9 |
> |
| 10 |
|
| 11 |
Is that necessarily a good idea? Given that the database formats are |
| 12 |
not compatible between versions without cleaning out the BDB |
| 13 |
environment files etc it seems like a source of conflict? |
| 14 |
|
| 15 |
Granted I'm not sure how this is used primarily in PHP, but for |
| 16 |
net-misc/sks I just stick to a known good stable slot (in that case |
| 17 |
4.8) and if switching that in the future expecting a news item or at |
| 18 |
least an elog pointing to the upstream UPGRADING instructions[0] |
| 19 |
|
| 20 |
References: |
| 21 |
[0] |
| 22 |
https://bitbucket.org/skskeyserver/sks-keyserver/src/867fbbe9720c269761472a64f047d416021a4e4a/UPGRADING?at=default&fileviewer=file-view-default |
| 23 |
|
| 24 |
-- |
| 25 |
Kristian Fiskerstrand |
| 26 |
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net |
| 27 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
Archives