Re: [rt-users] plugins link to module file, not package file

2014-12-11 Thread Alex Peters
I don't think there's anything to misunderstand here any more. The gist of what Jo conveyed is basically this (and it's all verifiably conveyed in earlier messages): I have 20 years of experience with Perl and use CPAN fairly often, yet when I'm presented with a CPAN link to the main module of a

Re: [rt-users] plugins link to module file, not package file

2014-12-11 Thread Jo Rhett
The levels of abuse and rudeness here are phenomenal. Alex has got his A-hole meter turned up to full strength. And if this list is moderated at all, I’m asking for Alex to be moderated. I’m filing a formal complaint with Best Practical over this. The funniest bit is that his instructions are

Re: [rt-users] plugins link to module file, not package file

2014-12-11 Thread Milt Epstein
Thought I'd chime in here. My background: I've been on this list for several months; I work at a site that's been using RT for several years -- I co-manage our installation; I joined the list because I needed to figure out a few things, and then stayed on it because it was low volume and

Re: [rt-users] plugins link to module file, not package file

2014-12-11 Thread Alex Vandiver
On 12/11/2014 01:14 PM, Milt Epstein wrote: Thought I'd chime in here. [...] And I'm going to step in before this gets any further out of hand. The amount of high dudgeon in this thread is not acceptable. If it continues, I _will_ turn on list moderation. Don't make me turn this car around,

Re: [rt-users] plugins link to module file, not package file

2014-12-11 Thread Alex Peters
I support the idea of switching to MetaCPAN, which seems to be in active development and seems to generally get a lot more right in terms of modern website development. Plus, Download links are on the left there instead of the right. We've established that this is important. ;) Since RT

Re: [rt-users] plugins link to module file, not package file

2014-12-10 Thread Jo Rhett
I’ve been using Perl for 20 years now. I grok perl. Good run with the insults and rudeness. Because yeah, that’s a great way to treat someone who’s pointing out a way to improve the usability of something. Treat them like dirt, and talk down to them like they’ve never used Perl before. I’ll

Re: [rt-users] plugins link to module file, not package file

2014-12-10 Thread rick
Jo, I honestly think that Alex simply misunderstood you. That's not uncommon in these kind of lists. Better to not attribute to malice what can be explained by miscommunication. Even in the very rare occasion that it _is_ malice, you are better off assuming the best of people. - Rick I’ve been

Re: [rt-users] plugins link to module file, not package file

2014-12-10 Thread Alex Peters
No problem. Sorry to see you go. On Thu, 11 Dec 2014 12:49 pm Jo Rhett jrh...@netconsonance.com wrote: I’ve been using Perl for 20 years now. I grok perl. Good run with the insults and rudeness. Because yeah, that’s a great way to treat someone who’s pointing out a way to improve the

Re: [rt-users] plugins link to module file, not package file

2014-12-09 Thread Alex Peters
I feel that there are actually several issues to discuss in this thread: 1. Perl modules vs. Perl module distributions 2. Perl module distribution sources 3. Perl module distribution installation 4. knowledge assumed by the CPAN site 5. knowledge assumed by RT's documentation 6.

Re: [rt-users] plugins link to module file, not package file

2014-12-08 Thread Jo Rhett
So here’s my perspective. As someone with 25 years of sysadmin experience, who has both used RT for many years (but not in the last three years) and someone who uses CPAN fairly often, when sent to the pm module directly, I did the operations directly in front of me and downloaded the .pm and

Re: [rt-users] plugins link to module file, not package file

2014-12-08 Thread Christian Loos
Am 08.12.2014 um 19:09 schrieb Jo Rhett: Which is said where and how? The point is to improve the documentation such that available paths for installation are clear. Your suggestion for yet another undocumented path is just further argument that the extensions documentation should be

Re: [rt-users] plugins link to module file, not package file

2014-12-03 Thread Christian Loos
Am 03.12.2014 um 10:40 schrieb Jo Rhett: As I just said, asking the user to edit the URL in their browser window to be able to find the extension to download doesn’t make a lot of sense. The links in the directory should be fixed. Why do you want to download the extension? You can install them

Re: [rt-users] plugins link to module file, not package file

2014-12-03 Thread Alex Peters
I think I might be missing something crucial in what you are saying/asking. Linking to the main module within a distribution is a very common practice, because that module is likely to have the most relevant documentation for that distribution. The distribution is clearly linked to on the page

Re: [rt-users] plugins link to module file, not package file

2014-12-02 Thread Jo Rhett
Hey, dunno if this got overlooked during the short vacation week. This is a pretty serious issue… asking users to manually hack up the URL in their browser bar is not accessible. On Nov 26, 2014, at 2:22 PM, Jo Rhett jrh...@netconsonance.com wrote: Hey guys and gals, been a long time. I’m

Re: [rt-users] plugins link to module file, not package file

2014-12-02 Thread Alex Peters
Could you please clarify what you're asking here? How to install the plugins? The plugins can be installed like any other CPAN module. Given a link to a specific .pm file: http://search.cpan.org/dist/RT-Extension-MandatorySubject/lib/RT/Extension/MandatorySubject.pm you can hit the Download

[rt-users] plugins link to module file, not package file

2014-11-26 Thread Jo Rhett
Hey guys and gals, been a long time. I’m doing an upgrade from 3.8.5 to 4.2. It seems to be going well. I’m liking the changes. Other than some confusion about what order to do things in (see my other message) the one thing I can’t seem to wrap my head around is the new plugin setup. First,