Re: Intoroduction: pmcenery
- To: email@example.com
- Cc: firstname.lastname@example.org
- Subject: Re: Intoroduction: pmcenery
- From: Paul McEnery <email@example.com>
- Date: Fri, 22 Jan 2010 16:21:03 +0000
- Message-id: <firstname.lastname@example.org>
- In-reply-to: <20100122153944.GI4308@belanna.comodo.priv.at>
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <20100122153944.GI4308@belanna.comodo.priv.at>
2010/1/22 gregor herrmann <firstname.lastname@example.org>:
> On Thu, 21 Jan 2010 20:29:56 +0000, Paul McEnery wrote:
>> - dget http://mentors.debian.net/debian/pool/main/s/slimrat/slimrat_1.0-1.dsc
> I haven't looked at the package yet, just a few general comments:
>> I'll checkout the project page and wiki for answers to my other
>> questions, such as what the preferred packaging practices are and VCS
>> for packaging. My personal preference is debhelper (new short rules)
>> and Git.
> In general the Debian Perl Group packages modules and not
> applications; then there are some corner cases and then we also have
> very few real applications :)
Thanks for your comments Gregor.
I guess for me the question is; Am I doing the right thing by
attempting to get this application into the project repository. At the
end of the day, the Maintainer field is going to be changed to
"pkg-perl-maintaintainers". This I guess gives it some collective
responsibility - although I'm committed to maintaining it. The other
question pertains to a sponsor. Is anyone willing to put there hand up
and sponsor it when all is said and done?
> Ad VCS:
> Our main working area is our svn repo, which contains ~1500 module
> packages in trunk/ and an empty apps/ directory :)
> This svn repo (actually only the trunk/ dir) is monitored with PET:
> http://pkg-perl.alioth.debian.org/cgi-bin/pet.cgi which is our main
> cooperation tool. IIRC all documentation also refers only to svn.
Sounds like I should be putting it in apps, but this is not going to
be monitored. I guess this again comes back to the question of should
I be trying to become part of something that was maybe - never meant
I suspect the answer lies in what "Section" the package falls. In this
case, its "net". I've just been looking at the "backuppc" application
and see that it is not packaged here in debian-perl. Possibly this
means I should simply be seeking someone outside of debian-perl to
> Then there is a git repository which contains a few apps and some
> modules. It's used by very few people and doesn't show up on PET yet
> (PET's multi-repo support and git support are still work in
> Since slimrat sounds more like an application than a module and since
> you prefer git, it sounds like putting it in
> git+ssh://git.debian.org/git/pkg-perl/apps/slimrat.git might be
> appropriate. Please note that you'd have to hunt down people to
> review and upload it on your own because of the PET limitations.
> Ad package helpers:
> You'll find enough documentation about that on the group's pages;
> just as a short note: almost everybody prefers and uses the modern
> short debhelper stuff just like you :)
>> When the package is in the right shape, will I be allowed to
>> put it into one of the VCS's?
> Since you're a group member, go ahead and use svn and/or git!
Any discussion on this is welcome, as I think I'm stuck until some
decision is made.