On 2013-08-15 09:14:39, olivier sallou wrote:
> Le 15 août 2013 08:58, "Marcin Kulisz" <firstname.lastname@example.org> a écrit :
> > > Right now the "release" cycle of the python version is simply tooIf you're talking about shell version I my opinion it's no go as it's
> > > rapid to make a packaged version and I am unsure whether it is going
> > > to slow down sufficiently over the next year to actually release a
> > > packaged version.
> > To be honest I started working on packaging python version and should have
> > something once I'm back home from my holiday (another few weeks).
> > Once it's build I'm going to drop it into alioth and mentors and will drop an
> > info into this list that it's ready.
> Let's focus on a version considered stable by Anders (tagged in github) for
> python version.
downloading resources from 3rd party sites like euca2ools, boto patches etc..
I don't think it's appropriate or policy valid to put such kind of soft into
archive. Of course we can remove those obstructions, but question is how far
away are we from having python version available.
Beside after short conversation with Anders I prefer not to put current
'stable' version into Debian archive.
Hopefully I won't reveal any secret that Anders is very close to release alpha
version for the python rewrite.
Np will do it.
> Once package is ready and dropped to mentors, put me in copy, I will try to
> mentor the package.
I the mean time if you want to use package I prepared for master branch I can
reupload it to mentors just let me know.
It's build on the latest commit from master with small patch to make Debian
|_|_|0| "Heghlu'Meh QaQ jajVam" |
|0|0|0| -------- kuLa --------- |
gpg --keyserver pgp.mit.edu --recv-keys 0x58C338B3
3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3