> From: Allison Randal [mailto:[EMAIL PROTECTED] > > 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.
Lots of work for us! :-) > 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. I am helping Jos work on the cpan++ tool which right now builds the phalanx 100 perl modules daily. We are trying to get this to work under debian, it currently does not. Debian packages however need some gentle loving care by an actual human. While package building often can be automated, it is hard to upload automated packages into debian for various technical and not so technical reasons. > > Usually the debian maintainer is responsible for forwarding bugs, > > since parrot is maintainer-less it appears that this didn't > happen. I > > will look into this and see if I can forward them. > > Thanks, that would be helpful. We'll change the primary > maintainer in the next Debian Parrot package to "Parrot > Porters <[EMAIL PROTECTED]>" with the 6 release > managers listed in "Uploaders", following the recommendation > for collaborative maintenance > in: > <http://www.debian.org/doc/manuals/developers-reference/ch-pkg > s.en.html#s-collaborative-maint> That document assumes that the team "parrot-porters" is a group of debian developers working together to maintain parrot in debian, it is a document aimed at debian developers. However I cannot find a debian team called "parrot-porters". I assume this is the name that the parrot project uses for those who are porting parrot to various platforms. What you'll want to do is have someone who is a debian developer (DD) or debian maintainer (DM) to upload your packages into debian and have them be the official maintainer. This is what we do in the perl group, so when a bug report comes for one of the 300+ packages we maintain, any one of us can fix it. If you can't find a DD you can have someone become a DM which is a much less time intensive process, though it obviously helps if he or she has experience packaging for debian since they get upload rights. In short, "teams" i.e. debian-perl are internal debian groups with upload rights. > > The debian perl group ([EMAIL PROTECTED]) is > usually quite > > helpful if you are going to package perl-related software. > > Thanks for the introduction. And, to the whole group: we're > looking for a Debian Developer to sponsor the Parrot Debian > packages. Let us know if you have any recommendations. > Someone with experience packaging a virtual machine (like > Mono or Java) or interpreter (like Perl or Python) would be > helpful to answer our questions as we automate the Debian > packaging process. The debian-perl team mainly packages perl modules, we explicitly do not package the interpreter "perl". > I also have some other Debian developer contacts, so I'll ask > around and see what we can come up with. Excellent, if you already know someone that is often the fastest way to get your packages sponsored. But I am certain someone inside debian with the required experience will come forward and help out with parrot since it is such a high profile project. Jeremiah
