One way to do development from git repos is something like:
- clone RT from git in a working directory
- clone new extension repos into another working directory
- set the RTHOME environment variable to the location of your test RT
- run the typical perl Makefile.PL; make install for the extension
- restart RT (either Apache or standalone dev server)
The installer puts files in different places under RT’s local directory
so they get picked up by RT properly. It would likely be a fair bit of
hacking to try to fake it out. We usually just create a simple shell
alias for the install steps so we can do something like:
- open files in extension
- code, code, code
- run ‘install’ alias, or whatever you want to call it
- test on the RT side
You can also put the RT restart command in your alias so everything gets
reloaded when you install more code.
It’s not too much overhead and the good part is when you’re done you
know that the extension should install as expected for others.
If you haven’t found it yet, this should help as well:
https://bestpractical.com/docs/rt/4.2/writing_extensions.htmlOn 2/24/16 5:05 AM, Joachim Schiele wrote:
=== Q1 running RT from GIT + plugin from GIT ===
i want to get the REST2 plugin, and later my own plugin going with RT
4.2.12 but i don’t want to install either using CPAN yet as i want to
modify the sources.
is there a way like placing a symlink in rt/lib to rt-extension-rest2/
…/…/rt-extension-rest2/lib/RT/Extension/REST2* or something similar?
=== Q2 extension install path ===
if i install a extension it will usually be installed into the /rt path
and not as normal CPAN modules into $somewhere from where it is
referenced using PERL5LIB
is that the only way to install a plugin?
thanks for help!
joachim & paul
RT 4.4 and RTIR Training Sessions (http://bestpractical.com/services/training.html)
- Hamburg Germany - March 14 & 15, 2016
- Washington DC - May 23 & 24, 2016