[SEToolkit-developer] Miscellaneous notes

[Tankersley, J. <jon...@ed...>]

I had to 'rebuild' a package so that I could hand it off to someone who
doesn't want to understand anything.....

I didn't start with the full SVN pkg yet, but I did notice some changes
to the old package that need to be made, and that would have to be check
with the new packaging scheme.
Or we COULD just build a separate package for Orca that has a dependency
on the SEToolkit package.

Binaries move to libexec
Bin/se script has that change included

To INCLUDE Orca we should somehow include the Orca and Adrian's
extensions.
Here's what I did to hack the new stuff into the old package.

Trunk/se/adrian copied to /opt/RICHPse/adrian
Trunk/orca/lib/SE copied to /opt/RICHPse/lib along with symlinks to have
3.4.x per the version information.
Orcallator startup scripts modified to have
-I/opt/RICHPse/adrian/include and -I/opt/RICHPse/lib/SE/3.4.x
Orcallator/orcallator.se.490 - svn version 490 of the orcallator script
included - orcallator.se is symlinked to this file.
Various binaries appropriately installed in the libexec directory.

This is enough to get the orcallator script to launch properly.

Any thoughts?