Ralf, I rather feared that the --makeproxy option was meant for creating RPM's in another hierarchy. (Now that I found the implementation and documentation in mkproxyrpm.pl I see that it is well explained.) For my planned use two hierarchies would be a lot of extra work though - I would have to build my packages twice: once for the master hierarchy and once for the slave hierarchy so that slave can choose between have a local version or an NFS (proxy) version of the package (or am I missing a simpler solution?). I can override the link - but it would be nice if the correct master link was integral to the RPM. Would a patch to rpm that defines the master location when using --makeproxy (say --proxyprefix) be accepted or am I breaking the openpkg philosophy?
Martin > -----Original Message----- > From: Ralf S. Engelschall [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 18, 2002 3:05 AM > To: [EMAIL PROTECTED] > Subject: Re: makeproxy - was RE: openpkg newbie trying to > build rt from > curren t > ... > Wait, PROXY packages are not installed into the same > hierarchy for which > they are derived. The procedure actually is: > > $ <master>/bin/rpm --rebuild > ftp://ftp.openpkg.org/current/SRC/foo-X-Y.src.rpm > $ cd <client>/RPM/PKG > $ <client>/bin/rpm --makeproxy <master>/RPM/PKG/foo-*.rpm > $ <client>/bin/rpm -Uvh <client>/RPM/PKG/foo-*.rpm > > So, you use the RPM from the client hierarchy to build a proxy package > for it by referencing the binary RPM from the master > hierarchy. And the > proxy package then is installed into the client hierarchy. > This way you > do not get any circular references. > > ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
