On Mon, Jan 27, 2003 at 11:37:47AM +0100, Michael van Elst wrote:
>On Sun, Jan 26, 2003, Bill Campbell wrote:
>
>> The tripwire-2.3.1-2 SRC that appeared in the current/SRC directory tonight
>> build under SuSE 8.1, creating executables:
>> ./bin/i686-pc-linux_r/tripwire
>> ./bin/i686-pc-linux_r/twadmin
>> ./bin/i686-pc-linux_r/twprint
>> ./bin/i686-pc-linux_r/siggen
>
>
>Do you have STLport somewhere installed on your system ? The binaries
>are linked against stlport_gcc with that spec-file but the STLport
>sources that are embedded in the source tree are not compiled.
No, they're not installed although they are available on SuSE 8.1:
STLport-5.0.0409-28.i586.rpm
>Do the binaries appear to work ?
As far as I can tell they do. So far, all I've done is run them with
--help options, and that works.
I need to put together proper configuration files. We've been running
tripwire-1.30 for years (largely because I've been overwhelmed by the C++
oddities of the newer version :-). The versions as compiled now assume
locations in /etc/tripwire, /var/lib/tripwire, etc. which I would think
should be changed to comply with the openpkg standards.
I was going to suggest that some of the installation locations be changed,
and the availabile policy/*.txt files installed. I think that typical
older tripwire installations put the binaries under /var/adm/tcheck/bin
rather than in the normal executable PATH so it seems to me that it would
make sense to split things out into:
%{l_prefix}/libexec/tripwire
%{l_prefix}/etc/tripwire
%{l_prefix}/lib/tripwire
I would probably put the policy/*.txt files in the etc directory where
they're easily available as samples.
Bill
--
INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/
``Rights'' is a fictional abstraction. No one has ``Rights'', neither
machines nor flesh-and-blood. Persons... have opportunities, not rights,
which they use or do not use.
-- Lazarus Long
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
