Using the default install path, which path would a code overlay for
EmailParser.pm go in?
[1] /opt/rt3/lib/EmailParser_Local.pm
[2] /opt/rt3/local/lib/EmailParser_Local.pm
Also, would I only be putting the sub that I am trying to modify in the
EmailParser_Local.pm, or does the _Local.pm copy completely trump the
original file? From Jesse on the release of 3.0.0 RC1:
" * RT even easier to extend than ever before: The API is much
better documented, the web interface includes a new
“Callbacks”
mechanism to let you embed your own components without
touching
a line of RT’s source code. The core libraries include a new
“Overlay” system to let you override RT’s core functionality
at the subroutine level."
This seems to indicate the former condition - and that’s what I remember
from the training, I’m just a little confused, and am looking for some
guidance.
Thank you for your attention.
G. Richard Bellamy
Enterprise Solution Architect
Pteradigm - Evolutionary
mailto:rbellamy@pteradigm.com
V:707-869-3665
Using the default install path, which path would a code overlay for
EmailParser.pm go in?
[1] /opt/rt3/lib/EmailParser_Local.pm
[2] /opt/rt3/local/lib/EmailParser_Local.pm
Also, would I only be putting the sub that I am trying to modify in the
EmailParser_Local.pm, or does the _Local.pm copy completely trump the
original file? From Jesse on the release of 3.0.0 RC1:
" * RT even easier to extend than ever before: The API is much
better documented, the web interface includes a new “Callbacks”
mechanism to let you embed your own components without touching
a line of RT’s source code. The core libraries include a new
“Overlay” system to let you override RT’s core functionality
at the subroutine level."
This seems to indicate the former condition - and that’s what I remember
from the training, I’m just a little confused, and am looking for some
guidance.
Either of
/opt/rt3/lib/RT/EmailParser_Local.pm
/opt/rt3/local/lib/RT/EmailParser_Local.pm
will work. The “Local” files are found by perl using its standard
internal search path. So you could even throw them in
/usr/local/share/perl5/… if you wanted to, though we don’t recommend
it.
Thank you for your attention.
G. Richard Bellamy
Enterprise Solution Architect
Pteradigm - Evolutionary
mailto:rbellamy@pteradigm.com
V:707-869-3665
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
will work. The “Local” files are found by perl using its standard
internal search path. So you could even throw them in
/usr/local/share/perl5/… if you wanted to, though we don’t recommend
it.
… assuming that’s in your perl search path
use perl -V to see what @INC is.
-R