| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 02/02/2013 12:13 PM, Ciaran McCreesh wrote: |
| 5 |
> On Sat, 02 Feb 2013 12:06:39 +0100 hasufell <hasufell@g.o> |
| 6 |
> wrote: |
| 7 |
>> From a little discussion in this bug |
| 8 |
>> https://bugs.gentoo.org/show_bug.cgi?id=454600#c11 it seems that |
| 9 |
>> it's not entirely sure what bash version can be assumed. |
| 10 |
>> |
| 11 |
>> PMS says, that I have to assume 3.2 or later |
| 12 |
>> https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-620006 |
| 13 |
>> |
| 14 |
>> But there is no stable bash version from 3.2 to 4.1 portage |
| 15 |
>> itself depends on >=app-shells/bash-4.2_p37 |
| 16 |
> |
| 17 |
> It's irrelevant what Portage depends upon, since this is about the |
| 18 |
> upgrade path. PMS specifies what the Council voted upon last time |
| 19 |
> this came up. |
| 20 |
> |
| 21 |
|
| 22 |
Yeah, from what I read and after checking council logs I don't see any |
| 23 |
vote/discussion that would change this requirement. |
| 24 |
|
| 25 |
for reference: |
| 26 |
https://bugs.gentoo.org/show_bug.cgi?id=431340 |
| 27 |
|
| 28 |
I will push for allowing >=bash-4.0 in EAPI=6. |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 31 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 32 |
|
| 33 |
iQEcBAEBAgAGBQJRDP7XAAoJEFpvPKfnPDWzwykH/joNViLyZlVVqFUSM9w+FKfs |
| 34 |
i31Wegdo3WM7rJeeChyJW0JvI5e8VFzvkvLB116Z9VENFGMedEKLygtvTKYJRMt1 |
| 35 |
KmHdb5xmKf+v048u9YiWfAaseYOXlrnm3O6KoEVIGRB4LnqIhMOkmAu8MU6bTje7 |
| 36 |
ly7kaIEdga0E0OiCGKz7d3sXkVBnNBdjeUDdZfSYsQcEqE17lt1enuWiCfOn3dT6 |
| 37 |
BjCQvqN8pGU2t4CcAnWZuBUxefIv57/sC0qbzLiRvzPzeofc7hVcW7VeZDh4gi5j |
| 38 |
k27zGnJUlQKj2M3t3qUAg46Za1kEjlwpJbjvb2Dc3RoYR63gkFxg7nJuMyKZW4Y= |
| 39 |
=LgxJ |
| 40 |
-----END PGP SIGNATURE----- |
Archives