On 05/29/2013 06:24 AM, Maciej Dobrzanski wrote:
> While converting our customizations into proper extensions I discovered that
> the installer, which I grabbed from other existing extensions, writes files
> into both release as well as local code trees. This way modules from 'lib'
> always go to rt/local/lib/RT, but everything from 'html' such as Mason
> files, CSS, Javascript end up in rt/html instead of rt/local/html. The
> culprit appears to be here:
What RT version are you running?
Modern versions of Module::Install::RTx install all extension data into
local/plugins/Extension-Name/.
If you're seeing extension files installed into local/{lib,html} or
html/ then I suspect you're using an old version of
Module::Install::RTx, or perhaps a very old version of RT.
Rather than copying inc/ from another extension, you're better off
installing Module::Install::RTx from CPAN and then writing and running a
Makefile.PL which uses it. When you run it, it'll populate inc/ with
the latest code. You should also make sure that a inc/.author directory
exists for module authors _only_ since it will tell Module::Install to
regenerate files that it wouldn't otherwise do.
This draft documentation for writing extensions may be of help:
https://github.com/bestpractical/rt/blob/4.0/writing-rt-extensions-doc/docs/writing-extensions.pod
--
RT Training in Seattle, June 19-20: http://bestpractical.com/training
