Re: Specf file update

On Tue, 2004-02-10 at 01:37, Steve G wrote:
> Hi,
> 
> Attached is a patch that gets the rpm spec file finalized. 
<snip>
> . It has been tested on a RH 9 system and works perfect.

I applied these changes to the cvs and also added your mandrake init
script.

> However, a Mandrake system still does not build because it still
> thinks the distro is REDHAT. Something else changed in the
> makefiless. I noticed that it now runs configure twice. It didn't
> do that Sunday.

Mhh, I did two check-ins in different directories. Maybe this lead to
different file dates. 

I changed the rpm-based check a little bit, so that it looks for
/bin/rpm too when deciding if rpm should be run. Maybe that fixes the
mandrake detect problem. 

The code snipet for the check is now

--8<--

if test -f "/etc/rc.d/init.d/functions" || test -x "/usr/bin/rpm" || 
test -x "/bin/rpm" ; then

    if test -x "/usr/bin/rpm" || test -x "/bin/rpm"
    then
      echo "Your dist looks somewhat Redhat like, lets dig deeper"

      rpmversion=`rpm -qa | grep release| tr A-Z a-z`
      if test "x${rpmversion}" = "x" ; 
      then
         echo "rpm returned nothing"
      fi
    fi
  
    DISTRIB="REDHAT"
    DEBUG_FILE_DEFAULT=`eval echo $localstatedir`/log/tmdns.debug.log
    PID_FILE_DEFAULT=`eval echo $localstatedir`/run/tmdns.pid
    INIT_DIR=/etc/rc.d/init.d
    
    case "x$rpmversion" in
      *mandrake*)
        echo "Looks like you are running Mandrake"
        DISTRIB="MANDRAKE"
        ;;
      *redhat*)
        echo "Indeed it's RedHat"
        ;;
      *)
        echo "Can not identify your dist.($rpmversion)"
        echo "  falling back to RedHat defaults"
        ;;
    esac
 fi
--->8---

> Question: Is there a conflict between bind & tmdns on the same
> system? If there is, I need to add a conflict: bind to the rpm
> spec file.

No, there is no conflict and tmdns can even be used to allow bind to
resolve ".local" and link-local reverse zones, tmdns should then use a
differnt bridge port however. I run such a configuration on my
development box. I added a hint about that to the readme file which
includes the neccessary zone statements for "named.conf"

When tmdns is started after bind, it won't be able to bind to port 53
and just ignores the bridge setting.

Ciao
  Andi





-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn