On 12/16/2014 05:15 PM, Jo Rhett wrote:
It failed exactly that way for me, even though we did use the stock
directory. On a fresh installation on a fresh node with nothing on it
but CentOS 6 with the provided Perl and having followed your
instructions for installing all dependencies from CPAN.
On Dec 15, 2014, at 5:07 PM, Alex Vandiver ale...@bestpractical.com wrote:
I've just verified that all of BPS' packages that we list on the
Extensions page contain an INSTALLATION section which is up-to-date,
which I believe removes any necessity for common knowledge.
...
Do you think that
On 12/12/2014 02:39 AM, Jo Rhett wrote:
Linking to the documentation makes sense. Linking to the module docs
without any clear installation instructions does not.
On Dec 12, 2014, at 10:06 AM, Alex Vandiver ale...@bestpractical.com wrote:
Picking a commonly-used module, RT::Extension::SLA, and
On 12/14/2014 07:23 PM, Jo Rhett wrote:
I’m not sure where you are looking. I’m at
https://www.bestpractical.com/rt/extensions.html and it links to
https://metacpan.org/pod/RT::Extension::SLA without #INSTALLATION.
Sorry -- I did not mean to imply that our link contained the
#INSTALLATION
On Dec 15, 2014, at 2:20 PM, Alex Vandiver ale...@bestpractical.com wrote:
I was not trying to argue that we cannot make this simpler for new users
-- I agree that we can, and should. I was primarily addressing what
seemed to be your belief that most CPAN modules could be installed via
On 12/15/2014 06:20 PM, Jo Rhett wrote:
Again, back to “you must be a perl hacker to use RT”. My entire
point is that installation instructions can and should be
self-sufficient, without requiring a person to utilize “common
knowledge” of something they might not be experts in.
I've just
On 12/12/2014 02:39 AM, Jo Rhett wrote:
On Dec 11, 2014, at 11:26 AM, Alex Vandiver
ale...@bestpractical.com wrote:
Moving to the topic at hand: the links we provide are to the
documentation of the module, not to the distribution page. This
is intentional, soas to provide the user with a
