|
|
 Up |
|
|
  |
Author: Gabor SzaboGabor Szabo Date: May 20, 2008 08:10
Hi,
a month or two ago in Oslo we discussed with Jeremiah and others
that I would like to make it easy for everyone, including the CPAN module
authors to see which of the CPAN modules are distributed by Debian.
In addition I would like to add a kwalitee metric to CPANTS
http://cpants.perl.org/
indicating that the module is distributed by Debian without any local patches
and that it has no bugs reported in Debian.
I hope that having such metric on CPANTS will encourage CPAN developers
to make sure they pick up the patches from Debian and fix the bugs reported
in Debian.
So we figured out the best would be if there was a cron job on some
debian server
generating a csv file with fileds like
Perl-Package-Name,CPAN Version,Number of patches,Number of bugs,Link
to its home page in Debian
I guess I am talking about Debian Unstable here but we can discuss this.
I can then fetch this file and update the CPANTS database with this information.
|
| Show full article (1.42Kb) |
|
| | 28 Comments |
|
|
Author: MartÃn FerrariMartÃn Ferrari Date: May 20, 2008 08:30
Hi Gabor,
On Tue, May 20, 2008 at 12:04 PM, Gabor Szabo gmail.com> wrote:
> a month or two ago in Oslo we discussed with Jeremiah and others
> that I would like to make it easy for everyone, including the CPAN module
> authors to see which of the CPAN modules are distributed by Debian.
Jeremiah told us a little about this, and I'm very happy to see this initiative!
> I hope that having such metric on CPANTS will encourage CPAN developers
> to make sure they pick up the patches from Debian and fix the bugs reported
> in Debian.
Excellent!
> So we figured out the best would be if there was a cron job on some
> debian server
> generating a csv file with fileds like
> Perl-Package-Name,CPAN Version,Number of patches,Number of bugs,Link
> to its home page in Debian
Nowadays we don't have all that information, but let's examine it:
|
| Show full article (2.54Kb) |
|
| | 1 Comment |
|
|
Author: Gabor SzaboGabor Szabo Date: May 20, 2008 08:40
On Tue, May 20, 2008 at 6:20 PM, MartÃn Ferrari
gmail.com> wrote:> Hi Gabor,
>
> On Tue, May 20, 2008 at 12:04 PM, Gabor Szabo gmail.com> wrote:
>>> a month or two ago in Oslo we discussed with Jeremiah and others
>> that I would like to make it easy for everyone, including the CPAN module
>> authors to see which of the CPAN modules are distributed by Debian.
>
> Jeremiah told us a little about this, and I'm very happy to see this initiative!
>
>> I hope that having such metric on CPANTS will encourage CPAN developers
>> to make sure they pick up the patches from Debian and fix the bugs reported
>> in Debian.
>
> Excellent!
>
>> So we figured out the best would be if there was a cron job on some
>> debian server ...
|
| Show full article (3.03Kb) |
| no comments |
|
|
Author: MartÃn FerrariMartÃn Ferrari Date: May 20, 2008 08:40
On Tue, May 20, 2008 at 12:30 PM, Paul Wise debian.org> wrote:
>> - Perl-Package-name: we currently have a pointer to the homepage and
>> the watchfile which strongly suggest this (we almost always use
>> seach.cpan.org/dist/foo URLs). I played with the idea of having a more
>> specific metadata available. >
> Probably the hard part. Would the most reliable way be to look at the
> Contents files and convert file names to Perl-Package-names?
It'd be much easier to look at the debian/watch file and infer from that:
$ perl -lne 'm# http://search.cpan.org/dist/(.+?)(?:/|$|\s)# and print
$1' debian/watch
SOAP-Lite
This would work for 99%% of our packages. But it is still very hackish.
--
MartÃn Ferrari
--
To UNSUBSCRIBE, email to debian-perl-REQUEST@ lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@ lists.debian.org
|
| |
| no comments |
|
|
Author: Paul WisePaul Wise Date: May 20, 2008 08:40
On Tue, May 20, 2008 at 11:20 PM, MartÃn Ferrari
gmail.com> wrote:
> Nowadays we don't have all that information, but let's examine it:
>
> - Perl-Package-name: we currently have a pointer to the homepage and
> the watchfile which strongly suggest this (we almost always use
> seach.cpan.org/dist/foo URLs). I played with the idea of having a more
> specific metadata available.
Probably the hard part. Would the most reliable way be to look at the
Contents files and convert file names to Perl-Package-names?
|
| |
| no comments |
|
|
Author: MartÃn FerrariMartÃn Ferrari Date: May 20, 2008 08:40
On Tue, May 20, 2008 at 12:28 PM, Gabor Szabo gmail.com> wrote:
> So if you or anyone can start to generate the CSV file with the already
> available data, I could then add it to CPANTS.
>
> We don't have to wait till everything is perfect. The rest of the data
> can be added later.
> This might also encourage other maintainers to use the same format
> making it easier to collect that info.
--
MartÃn Ferrari
--
To UNSUBSCRIBE, email to debian-perl-REQUEST@ lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@ lists.debian.org
|
| |
| no comments |
|
|
Author: Paul WisePaul Wise Date: May 20, 2008 08:50
On Tue, May 20, 2008 at 11:36 PM, MartÃn Ferrari
gmail.com> wrote:> On Tue, May 20, 2008 at 12:30 PM, Paul Wise debian.org> wrote:
>>>> - Perl-Package-name: we currently have a pointer to the homepage and
>>> the watchfile which strongly suggest this (we almost always use
>>> seach.cpan.org/dist/foo URLs). I played with the idea of having a more
>>> specific metadata available. >>
>> Probably the hard part. Would the most reliable way be to look at the
>> Contents files and convert file names to Perl-Package-names?
>
> It'd be much easier to look at the debian/watch file and infer from that:
>..
> This would work for 99%% of our packages. But it is still very hackish.
Sure, but there are still perl packages outside pkg-perl and many of
those may not have watch files. I hope that they will be supported by
CPANTS too (to the extent possible).
|
| Show full article (0.91Kb) |
| no comments |
|
|
Author: gregor herrmanngregor herrmann Date: May 20, 2008 09:40
On Tue, 20 May 2008 23:43:52 +0800, Paul Wise wrote:
[ Perl-Package-name ]
>>> Probably the hard part. Would the most reliable way be to look at the
>>> Contents files and convert file names to Perl-Package-names?
>> It'd be much easier to look at the debian/watch file and infer from that:
>>..
>> This would work for 99%% of our packages. But it is still very hackish.
> Sure, but there are still perl packages outside pkg-perl and many of
> those may not have watch files. I hope that they will be supported by
> CPANTS too (to the extent possible).
dh-make-perl also has it's algorithm (by parsing Makefile.PL and
META.yml) but that needs a source package, so for packages outside of
pkg-perl Homepage: and or/debian watch are probably more useful.
Hm, maybe even re-translating libfoo-bar-perl to Foo::Bar would catch
most packages/modules.
Cheers,
gregor
|
| Show full article (1.33Kb) |
| no comments |
|
|
Author: gregor herrmanngregor herrmann Date: May 20, 2008 09:50
On Tue, 20 May 2008 12:20:42 -0300, MartÃn Ferrari wrote:
>> I hope that having such metric on CPANTS will encourage CPAN developers
>> to make sure they pick up the patches from Debian and fix the bugs reported
>> in Debian.
> Excellent!
Indeed, a very nice initiative.
> - CPAN version: got that from watchfiles.
If we take care of the version mangling there :)
> - Number of patches: the problem here is the many ways of doing this
> in debian; but in the Perl Group we have more or less standarised on
> using quilt, and the few remaining use dpatch/simple-patchsys which
> are quite similar. I guess this can be added pretty easily for us, not
> for Debian in general (there are many Perl packages maintained outside
> the group).
|
| Show full article (1.92Kb) |
| no comments |
|
|
|
|
|
Author: Gunnar WolfGunnar Wolf Date: May 20, 2008 12:20
MartÃn Ferrari dijo [Tue, May 20, 2008 at 12:20:42PM -0300]:
> Hi Gabor,
Hi, Gabor. Hi, MartÃn. :)
> (... SNIP ...)
> - Number of patches: the problem here is the many ways of doing this
> in debian; but in the Perl Group we have more or less standarised on
> using quilt, and the few remaining use dpatch/simple-patchsys which
> are quite similar. I guess this can be added pretty easily for us, not
> for Debian in general (there are many Perl packages maintained outside
> the group).
Umh... Well, we are steadily moving towards "quiltifying" our
patches. If there is a debian/patches directory (which means, either
quilt or dpatch are in use - makes no real difference for the data
Gabor requires), we could just count the number of files in it, maybe
even give links to easily download each of them straight off our
web-svn tree. If debian/patches does not exist... It's a bit harder to
find whether any upstream-provided file has been modified. Maybe
comparing (again, in SVN) branches/upstream/ /current to
trunk. But this can be an expensive operation if done on request.
|
| Show full article (1.68Kb) |
| 1 Comment |
|
RELATED THREADS |
|
|
|
|
|
|
