More arch dependent shuffling needing

[Orion Poplawski]

Getting close, finally build the octave-forge rpm.  The following files 
ended up in /usr/share and need to be in /usr/libexec:

octave-forge.i386: E: arch-dependent-file-in-usr-share 
/usr/share/octave/packages/secs2d-0.0.3/Utilities/Ucompconst.oct
octave-forge.i386: E: arch-dependent-file-in-usr-share 
/usr/share/octave/packages/secs2d-0.0.3/Utilities/Ucomplap.oct
octave-forge.i386: E: arch-dependent-file-in-usr-share 
/usr/share/octave/packages/secs2d-0.0.3/Utilities/Ubern.oct
octave-forge.i386: E: arch-dependent-file-in-usr-share 
/usr/share/octave/packages/engine-1.0.3/liboct.a
octave-forge.i386: E: arch-dependent-file-in-usr-share 
/usr/share/octave/packages/audio-1.0.2/bin/aurecord
octave-forge.i386: E: arch-dependent-file-in-usr-share 
/usr/share/octave/packages/secs1d-0.0.3/Utilities/Ubern.oct
octave-forge.i386: E: arch-dependent-file-in-usr-share 
/usr/share/octave/packages/secs2d-0.0.3/Utilities/Uscharfettergummel.oct


So, looks like we (pkg.m) need to handle .oct files in sub-directories, 
binary executables and libraries.

In the specific case of aurecord, is this the same as the one provided 
by ttp://nas.codebrilliance.com?  In this case, I probably won't ship 
it.  However, in the general case, does octave add any of the package 
paths to the system search path?  The audio .m files simply run 
"aurecord" without any path.

With engine, how is this supposed to be used?  Files really should be in 
/usr/include and /usr/lib (or /usr/lib64) for development.  I guess 
someone could point elsewhere.  In any case, the .a needs to be in an 
arch specific directory.

Thanks everyone (esp. David Bateman) for your help with this.

--
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  address@hidden
Boulder, CO 80301              http://www.cora.nwra.com