Skip Menu |
 

This queue is for tickets about the AnyEvent CPAN distribution.

Report information
The Basics
Id: 111288
Status: rejected
Priority: 0/
Queue: AnyEvent

People
Owner: Nobody in particular
Requestors: JHI [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: AnyEvent *.pm files end in just "1"
Download (untitled) / with headers
text/plain 130b
As opposed to 1; This causes PPI to consider the *.pm files as "incomplete". And "1;" seems to be more common way across CPAN.
Subject: Re: [rt.cpan.org #111288] AnyEvent *.pm files end in just "1"
Date: Tue, 19 Jan 2016 17:01:06 +0100
To: Jarkko_Hietaniemi via RT <bug-AnyEvent [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
Hi! Please send your bug report to the official contact/author address for the module in question (or send it to rt.cpan.org@schmorp.de, that's fine as well). What follows is the rationale for this request, you don't have to read it if you don't care. Why is this necessary? rt.cpan.org has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with rt.cpan.org's bugs). Still, for some people, rt.cpan.org is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of rt.cpan.org didn't make their "service" optional - you can neither opt-in nor opt-out of rt.cpan.org as a module author. Just like a spammer, rt.cpan.org forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring rt.cpan.org is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss potentially vital bug reports such as yours (and of course it's a great impression if rt.cpan.org has lots of bug reports that are unanswered, making a module look unmaintained when in fact the opposite might be true). I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the rt.cpan.org providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the rt.cpan.org providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. One last issue: many people mail me that this can be "fixed" by including the bugtracker element in my module meta file. This is not true: 1. This field only affects search.cpan.org and maybe similar services. (Many people confuse rt.cpan.org with search.cpan.org for some reason). 2. It doesn't even work (there are still links to rt.cpan.org displayed). 3. Even if search.cpan.org does no longer display the link, it doesn't actually affect rt.cpan.org (and tests have shown that people go to rt.cpan.org regardless) Even *iff* rt.cpan.org would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like rt.cpan.org comes out, I would have to make dummy releases for all my modules. This not only creates a lot of extra work for me (I take releases very seriously) but also users, who would wonder why there is a new release. Thanks a lot, Marc Lehmann <rt.cpan.org@schmorp.de> Last updated: 2012-04-22
Download (untitled) / with headers
text/plain 297b
On 2016-01-19 03:05:36, JHI wrote: Show quoted text
> As opposed to > > 1; > > This causes PPI to consider the *.pm files as "incomplete". > > And "1;" seems to be more common way across CPAN.
I think this should be fixed in PPI -- it is valid perl for the last expression in a block to not end in a semicolon.
Download (untitled) / with headers
text/plain 460b
On Tue Jan 19 13:20:48 2016, ETHER wrote: Show quoted text
> On 2016-01-19 03:05:36, JHI wrote:
> > As opposed to > > > > 1; > > > > This causes PPI to consider the *.pm files as "incomplete". > > > > And "1;" seems to be more common way across CPAN.
> > I think this should be fixed in PPI -- it is valid perl for the last > expression in a block to not end in a semicolon.
Possibly. But how should I put this... maybe "the number of open issues in PPI is not promising".
I'm not interested in pursuing this issue.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.