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

  Server: cvs.openpkg.org                  Name:   Thomas Lotterer
  Root:   /e/openpkg/cvs                   Email:  [EMAIL PROTECTED]
  Module: openpkg-re                       Date:   19-Nov-2002 09:05:47
  Branch: HEAD                             Handle: 2002111908054700

  Modified files:
    openpkg-re              news.txt

  Log:
    remember makeproxy details

  Summary:
    Revision    Changes     Path
    1.10        +29 -0      openpkg-re/news.txt
  ____________________________________________________________________________

  Index: openpkg-re/news.txt
  ============================================================
  $ cvs diff -u -r1.9 -r1.10 news.txt
  --- openpkg-re/news.txt       19 Nov 2002 08:05:26 -0000      1.9
  +++ openpkg-re/news.txt       19 Nov 2002 08:05:47 -0000      1.10
  @@ -37,6 +37,35 @@
           remove all redundancy in the "perl-xxx" packages and get again a fully
           filesystem consistent packaging of all Perl stuff.
   
  +  o makeproxy
  +
  +        Date: Mon, 18 Nov 2002 19:17:34 +0100
  +        From: "Ralf S. Engelschall" <[EMAIL PROTECTED]>
  +        Subject: Re: makeproxy
  +        Message-ID: <[EMAIL PROTECTED]>
  +
  +        On Mon, Nov 18, 2002, Andrews, Martin wrote:
  +
  +        > The trick is that the master and client hierarchies are really the same
  +        > hierarchy (say /opt/openpkg) - but on different machines. I can use 
packages
  +        > created on the master on any machine (of the same platform). All machines
  +        > can also access the reference hierarchy from an automount point: say
  +        > /automount/openpkg-X-Y . As you mention, many packages will not work if I
  +        > try to run them from that location - but if I install a proxy package into
  +        > /opt/openpkg with links to the files in /automount/openpkg-X-Y then any
  +        > package can be supported!
  +
  +        Ah, ok, now I understand. Then it's sufficient that you have
  +        an option for overriding the remote/master path. Ok, done,
  +        see http://cvs.openpkg.org/chngview?cn=5464 for details and
  +        ftp://ftp.openpkg.org/current/SRC/openpkg-20021118-20021118.src.{rpm,sh}
  +        for the result. You now can use:
  +
  +        $ /usr/openpkg/bin/rpm --rebuild \
  +          ftp://ftp.openpkg.org/current/SRC/foo-X-Y.src.rpm
  +        $ rpm --makeproxy --prefix=/automount/openpkg-X-Y \
  +          /usr/openpkg/RPM/PKG/foo-X-Y.*.rpm
  +
     o ...
   
     Major changes between OpenPKG 1.0 and OpenPKG 1.1
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
CVS Repository Commit List                     [EMAIL PROTECTED]

Reply via email to