-=| Jonathan Yu, Wed, Jun 10, 2009 at 07:00:09PM -0400 |=-
On Wed, Jun 10, 2009 at 5:48 PM, Jeremiah
Foster<jeremiah@jeremiahfoster.com> wrote:
Maybe what is needed is the modularization of dh-make-perl in to
perl
modules and released on CPAN?
This is a very valid point. We need to work on exposing the
dh-make-perl internals so that other things like cpan2dist can use
it,
while not having to constantly update their stuff to keep in sync
with
policy. I'd also like to push for dh-make-perl to be release normally
via CPAN. Currently though I'm scared of the codebase, as it's fairly
messy stuff. damyan is brave :-)
Nah, I am just trying to clean up after contributing to the mess
dh-make-perl is.
Indeed though, a good long term goal is figuring out a good pattern
for exposing the API, so we can upload them as normal modules via
CPAN, and so they can be used directly by cpan2dist instead of having
to roll their own stuff.
I think that has the best outcome for everyone, and the DhMakePerl.pm
is a good first step in that direction.
No doubt here. What is missing is not consensus, but people doing the
work. I have ideas, possibly similar to yours, but I can't make them
real. Nights are too short.
Yes, the current code is a mess. So what? It is not rocket science.
And even if it was, we all are not that dummy. :)
So please, get involved. There is no argument that work needs to be
done. If you don't want where to start, there is a TODO in the
top-level directory. If you need assistance/guidance, just ask. Adding
to TODO is also OK. Filing wishlist bugs to the BTS -- too.
You want it on CPAN? So what is stopping you from uploading it there?
I am sure many of the subscribers of this list have CPAN accounts.
What stops you from using them? If changes are needed to shape
dh-make-perl for CPAN, don't sit on them, take the lead! If you aren't
sure, ask.