Hi,
I noticed something annoying in the install.sh script about manpages
installation :
first time you run it, it turns all .5 and .8 files into .5.gz and
.8.gz files, then copy them at the right place.
After the first run of install.sh script, ther is no more .5 and .8
files in the manpages directory.
But according to the extract of the script below, the second time you
run install.sh script, it starts with erasing .gz files so the manpages
is now an empty directory, turning the install.sh script to fail.
....
#
# Install the Man Pages
#
cd manpages
rm -f *.gz
^^^^^^^^^
for f in *.5; do
gzip $f
run_install -D -m 0444 $f.gz ${PREFIX}/usr/share/man/man5/$f.gz
echo "Man page $f.gz installed to /usr/share/man/man5/$f.gz"
done
for f in *.8; do
gzip $f
run_install -D -m 0444 $f.gz ${PREFIX}/usr/share/man/man8/$f.gz
echo "Man page $f.gz installed to /usr/share/man/man8/$f.gz"
done
cd ..
echo "Man Pages Installed"
.........
As part of an automated and repetitive build system for a firewall
distribution (devil-linux), the fact that install.sh script alters the
source installation directory is quite annoying : one has to untar the
archive each time one wants to install it.
I suggest either not to delete .gz files and modify accordingly the rest
of the script to recursively copy manpage files or to preserve original
.5 and .8 files using something like :
for f in *.5; do
gzip -c $f > $f.gz
....
Thanks for your wonderfull work,
MaNU ESCaR
occasional contributor to Devil-Linux Firewall Devel kit.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/