[Pkg-parrot-devel] Parrot 4.6.0, stable backports

[Alessandro Ghedini]

Hi all,

I've started packaging parrot 4.6.0 to avoid getting too much behind upstream
releases. You can find it in the topic/release-4.6.0 branch at [0].

The changelog so far looks like this:

parrot (4.6.0-1) UNRELEASED; urgency=low
 .
   * Team upload
   * New upstream release
   * Revert "Add patch to fix ia64 ftbs (hopefully)" since it didn't work
   * Add 04_fix_hurd_ftbfs.patch to fix build on hurd-i386.
     Thanks to Svante Signell (Closes: #686266)
   * Drop 01_use_icu-config_ldflags-libsonly.patch (merged upstream)
   * Generate binaries manpages from docs/binaries/ directory
   * Bump Standards-Version to 3.9.4 (no changes needed)

Also, sice 4.3.0 didn't make it to testing (and at this point it won't make it
to stable) I was thinking that we might upload 4.6.0 right away (once ready). I
was also thinking that we may provide stable backports on par with testing (once
wheezy is released) so that stable users would have access to newer parrot, nqp
and rakudo releases (given their development rate, even if parrot 4.3.0 & co
would have been in stable they would have become obsolete pretty quickly).

What do you think?

Cheers

[0] http://anonscm.debian.org/gitweb/?p=pkg-parrot/parrot.git;a=summary

-- 
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-parrot-devel/attachments/20121010/ea2602f9/attachment.pgp>