Hi Dave,
What about including the extensions (especially sial) in the crash rpm?
Or maybe even better, create a second crash-extensions sub package.
Michael
Here a proposal for the SPEC file change:
---
--- crash.spec.orig 2009-02-12 13:05:11.000000000 +0100
+++ crash.spec 2009-02-12 14:38:11.000000000 +0100
@@ -36,12 +36,25 @@
netdump, diskdump and kdump packages from Red Hat Linux, the mcore kernel patch
offered by Mission Critical Linux, or the LKCD kernel patch.
+%package extensions
+Summary: Additional commands for the crash dump analysis tool
+Group: Development/Debuggers
+
+%description extensions
+The extensions package contains plugins that provide additional crash
+commands. The extensions can be loaded in crash via the "extend" command.
+
+The following extensions are provided:
+* sial: Provides C-like language for writing dump analysis scripts
+* dminfo: Device-mapper target analyzer
+
%prep
%setup -n %{name}-%{version}-%{release}
# %patch0 -p1 -b .install (patch example)
%build
make RPMPKG="%{version}-%{release}"
+make RPMPKG="%{version}-%{release}" extensions
%install
rm -rf %{buildroot}
@@ -51,6 +64,8 @@
cp crash.8 %{buildroot}%{_mandir}/man8/crash.8
mkdir -p %{buildroot}%{_includedir}/crash
cp defs.h %{buildroot}%{_includedir}/crash
+mkdir -p %{buildroot}/usr/lib/crash
+cp extensions/*.so %{buildroot}/usr/lib/crash
%clean
rm -rf %{buildroot}
@@ -63,3 +78,7 @@
%files devel
%defattr(-,root,root)
%{_includedir}/*
+
+%files extensions
+%defattr(-,root,root)
+/usr/lib/crash/*
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
