| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 30/06/14 04:46 AM, Andreas K. Huettel wrote: |
| 5 |
|
| 6 |
> [snip!] * As Fabian pointed out, perl-core/Switch-2.160.0 should |
| 7 |
> still go stable. Fine with me (but I can't read your minds about |
| 8 |
> future stabilizations, and the virtual only had ~arch reverse |
| 9 |
> deps). |
| 10 |
> |
| 11 |
|
| 12 |
There shouldn't be any need to read minds, here -- if the previous |
| 13 |
stable perl had this capability, then the new stable perl should too |
| 14 |
(whether that be via internal or external module package). If it |
| 15 |
doesn't, then the upgraded-new-stable-perl isn't a valid replacement |
| 16 |
for the stable version it previously replaced. Remember that there |
| 17 |
could be who knows what scripts on end-user systems that need this |
| 18 |
functionality, and if it's suddenly not available because the only |
| 19 |
thing that provides it is ~arch, then they are not left in a happy state.. |
| 20 |
|
| 21 |
That's the case here, perl-core/Switch is still ~arch, therefore the |
| 22 |
current stable provider of Switch is still perl-5.12. Once the |
| 23 |
keywording is resolved though then 5.12 (and the virtual) would no |
| 24 |
longer be needed. |
| 25 |
|
| 26 |
It would be nice if something like a pkgmove be done on the virtual, |
| 27 |
though, upon its elimintation; anyone that installed the virtual to |
| 28 |
obtain perl Switch shouldn't have to unmerge and specifically emerge |
| 29 |
perl-core/Switch. I'm not sure if pkgmove itself supports this, though.. |
| 30 |
|
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 34 |
|
| 35 |
iF4EAREIAAYFAlOxfz4ACgkQ2ugaI38ACPCPZgD/e5g4fsbhBDKqo3Yal5/xc4Bc |
| 36 |
4M8CqdhKYAC5OCo8/ywBAIwIgdWDuJfL8vILLbfIIzi//kuSXllU6TcR/aCMOdlf |
| 37 |
=9AEF |
| 38 |
-----END PGP SIGNATURE----- |
Archives