[gentoo-dev] bash-4 in ebuilds?

2013-02-02 Thread hasufell 
From a little discussion in this bug
https://bugs.gentoo.org/show_bug.cgi?id=454600#c11
it seems that it's not entirely sure what bash version can be assumed.

PMS says, that I have to assume 3.2 or later
https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-620006

But there is no stable bash version from 3.2 to 4.1
portage itself depends on =app-shells/bash-4.2_p37

Is this a PMS bug or do we need to redefine this for EAPI=6?

Re: [gentoo-dev] bash-4 in ebuilds?

2013-02-02 Thread hasufell 
On 02/02/2013 12:06 PM, hasufell wrote:
 portage itself depends on =app-shells/bash-4.2_p37
 

strike that

|| ( =app-shells/bash-4.2_p37[readline] ( app-shells/bash-4.2_p37
=app-shells/bash-3.2_p17 ) )

!app-shells/bash-3.2_p17

Re: [gentoo-dev] bash-4 in ebuilds?

2013-02-02 Thread Ciaran McCreesh 
On Sat, 02 Feb 2013 12:06:39 +0100
hasufell hasuf...@gentoo.org wrote:
 From a little discussion in this bug
 https://bugs.gentoo.org/show_bug.cgi?id=454600#c11
 it seems that it's not entirely sure what bash version can be assumed.
 
 PMS says, that I have to assume 3.2 or later
 https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-620006
 
 But there is no stable bash version from 3.2 to 4.1
 portage itself depends on =app-shells/bash-4.2_p37

It's irrelevant what Portage depends upon, since this is about the
upgrade path. PMS specifies what the Council voted upon last time this
came up.

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature

Re: [gentoo-dev] bash-4 in ebuilds?

2013-02-02 Thread hasufell 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/02/2013 12:13 PM, Ciaran McCreesh wrote:
 On Sat, 02 Feb 2013 12:06:39 +0100 hasufell hasuf...@gentoo.org
 wrote:
 From a little discussion in this bug 
 https://bugs.gentoo.org/show_bug.cgi?id=454600#c11 it seems that
 it's not entirely sure what bash version can be assumed.
 
 PMS says, that I have to assume 3.2 or later 
 https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-620006
 
 But there is no stable bash version from 3.2 to 4.1 portage
 itself depends on =app-shells/bash-4.2_p37
 
 It's irrelevant what Portage depends upon, since this is about the 
 upgrade path. PMS specifies what the Council voted upon last time
 this came up.
 

Yeah, from what I read and after checking council logs I don't see any
vote/discussion that would change this requirement.

for reference:
https://bugs.gentoo.org/show_bug.cgi?id=431340

I will push for allowing =bash-4.0 in EAPI=6.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRDP7XAAoJEFpvPKfnPDWzwykH/joNViLyZlVVqFUSM9w+FKfs
i31Wegdo3WM7rJeeChyJW0JvI5e8VFzvkvLB116Z9VENFGMedEKLygtvTKYJRMt1
KmHdb5xmKf+v048u9YiWfAaseYOXlrnm3O6KoEVIGRB4LnqIhMOkmAu8MU6bTje7
ly7kaIEdga0E0OiCGKz7d3sXkVBnNBdjeUDdZfSYsQcEqE17lt1enuWiCfOn3dT6
BjCQvqN8pGU2t4CcAnWZuBUxefIv57/sC0qbzLiRvzPzeofc7hVcW7VeZDh4gi5j
k27zGnJUlQKj2M3t3qUAg46Za1kEjlwpJbjvb2Dc3RoYR63gkFxg7nJuMyKZW4Y=
=LgxJ
-END PGP SIGNATURE-