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

  Server: cvs.openpkg.org                  Name:   Ralf S. Engelschall
  Root:   /v/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-src                      Date:   25-Aug-2006 10:53:58
  Branch: HEAD                             Handle: 2006082509535700

  Modified files:
    openpkg-src/openpkg     root.README

  Log:
    now with the setuid wrapper it becomes more and more important to go
    through the 'openpkg' command and not by-pass it, so teach people the
    canonical way of running the rc-scripts (although setuid is a NOP for
    --eval here in case of a regular user calling this)

  Summary:
    Revision    Changes     Path
    1.5         +2  -2      openpkg-src/openpkg/root.README
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: openpkg-src/openpkg/root.README
  ============================================================================
  $ cvs diff -u -r1.4 -r1.5 root.README
  --- openpkg-src/openpkg/root.README   16 Feb 2004 21:06:51 -0000      1.4
  +++ openpkg-src/openpkg/root.README   25 Aug 2006 08:53:57 -0000      1.5
  @@ -14,8 +14,8 @@
     $ @l_prefix@/bin/openpkg rpm -qlv <name>
       (q)uery (v)erbose (l)ist of installed files of package <name>
   
  -  Use "eval [EMAIL PROTECTED]@/etc/rc --eval all env`" from within a user's
  -  Bourne (Again) Shell startup script (.profile or .bashrc) in
  +  Use "eval [EMAIL PROTECTED]@/bin/openpkg rc --eval all env`" from within a
  +  user's Bourne (Again) Shell startup script (.profile or .bashrc) in
     order to activate this hierarchy and all of its packages.
   
     In case of any questions or problems post to the OpenPKG project
  @@ .
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [email protected]

Reply via email to