Allison Randal dijo [Wed, Dec 19, 2007 at 02:14:35PM +0200]: > Indeed. Parrot is a complete virtual machine similar to Mono or > Java. As such, it's likely that Parrot will ultimately split into a > few more packages than it currently has, including parrot-modules, > parrot-dev, and packages for running specific languages on Parrot, > such as parrot-perl6, parrot-perl5, parrot-python, parrot-ruby, etc.
Umh... I guess that Parrot can start linked to the pkg-perl group - It is already in Debian [1], however, is currently maintained by Florian Ragwitz (I'm adding him on Cc: - Florian, please refer to this thread's history [2]), so I think you should also coordinate with him. Note that the latest packaged Parrot is 0.4.13, last updated in June... Oh... I just noticed: Parrot has been marked as Orphaned - This means, Florian stepped down from maintaining it. So we _do_ need to find people to carry it on. It's _not_ a module similar to what we deal with in pkg-perl, and I'm sure it will increase in complexity and in demand for maintainer time - So we do need to get somebody with proper involvement and knowledge to maintain it! I see it's mainly C-based... So I'm not a prime candidate for it. However, although Parrot is AFAIK much closer linked with Perl today than with any of the other proposed languages, I think Parrot is a prime candidate for setting up its own Alioth project for proper Debian integration. > But, our focus at the start will just be getting the existing > packages updated to the current version of Parrot (0.5.1, released > yesterday) and resolving the issues noted in your issue tracker. The > next step is automating the process of producing the Debian > packages, so we can generate them as part of our monthly releases. Umh... Ok, here's my point of view: Of course you can do the Debian packages and release them, you are more than welcome... But I do think that the Debian packages belong _in_ Debian. Proper integration with the rest of the distribution (specially given that Parrot will likely become a major infrastructure base in the future) is not a trivial task, and we will have to deal with lots of cross-dependencies, migrations with version bumps of any of the affected languages, etc. I think that, if the Parrot developers want to get involved in maintaining Parrot fresh and up to date in Debian (and I think you should! ;-) ), the best way would be to get involved in the corresponding Alioth project. Probably even somebody in the Parrot development group becoming a Debian Maintainer... Greetings, [1] http://packages.qa.debian.org/p/parrot.html [2] http://lists.debian.org/debian-perl/2007/12/msg00134.html -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
