OpenPKG CVS Repository
  http://cvs.openpkg.org/
  ____________________________________________________________________________

  Server: cvs.openpkg.org                  Name:   Torsten Homeyer
  Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-src                      Date:   31-May-2006 16:13:16
  Branch: HEAD                             Handle: 2006053115131600

  Modified files:
    openpkg-src/nagios      nagios.spec

  Log:
    fixed permissions and log path on files in the plugin directory

  Summary:
    Revision    Changes     Path
    1.60        +5  -1      openpkg-src/nagios/nagios.spec
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-src/nagios/nagios.spec
  ============================================================================
  $ cvs diff -u -r1.59 -r1.60 nagios.spec
  --- openpkg-src/nagios/nagios.spec    24 May 2006 18:52:27 -0000      1.59
  +++ openpkg-src/nagios/nagios.spec    31 May 2006 14:13:16 -0000      1.60
  @@ -37,7 +37,7 @@
   Group:        Network
   License:      GPL
   Version:      %{V_nagios}
  -Release:      20060524
  +Release:      20060531
   
   #   package options
   %option       with_perl   yes
  @@ -89,6 +89,9 @@
       %setup -q -T -D -a 1
       %setup -q -T -D -a 2
       %patch -p0
  +    %{l_shtool} subst \
  +        -e 's;/usr/local/nagios/var/;%{l_prefix}/var/nagios/log;' \
  +        p1.pl
   
   %build
       #   configure and build Nagios
  @@ -171,6 +174,7 @@
       mv  $RPM_BUILD_ROOT%{l_prefix}/bin/p1.pl \
           $RPM_BUILD_ROOT%{l_prefix}/libexec/nagios/p1.pl
   %endif
  +    chmod 0755 $RPM_BUILD_ROOT%{l_prefix}/libexec/nagios/utils.sh
       rm -rf $RPM_BUILD_ROOT%{l_prefix}/var/nagios/archives
       rm -rf $RPM_BUILD_ROOT%{l_prefix}/libexec/nagios/share
   
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to