Ralf, 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!
Martin > -----Original Message----- > From: Ralf S. Engelschall [mailto:[EMAIL PROTECTED]] > Sent: Monday, November 18, 2002 11:30 AM > To: [EMAIL PROTECTED] > Subject: Re: makeproxy > > > On Mon, Nov 18, 2002, Andrews, Martin wrote: > > > 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? > > Do I understand correctly? You want... > > $ <client>/bin/rpm --makeproxy <master>/RPM/PKG/foo-*.rpm > > ...creates a package for <client> instance by using a package from > <master> which after installing into <client> references the stuff in > <master> while... > > $ <client>/bin/rpm --makeproxy --proxyprefix=<master2> > <master>/RPM/PKG/foo-*.rpm > > ...creates a package for <client> instance by using a package from > <master> which after installing into <client> references the stuff in > <master2>. Right? > > That's not a problem to add, but I still do not see how it solves > your "I've to build a package twice" problem. Because even after... > > $ <client>/bin/rpm --rebuild > ftp://ftp.openpkg.org/current/SRC/foo-X-Y.src.rpm > $ <client>/bin/rpm --makeproxy --proxyprefix=<master> > <client>/RPM/PKG/foo-*.rpm > > ..you just end up with the two packages for the <client>. But > nevertheless you still need the foo package for <master>, because > you usually in general cannot install the <client>/RPM/PKG/foo-*.rpm > into <master>. For simple packages (those which do not reference own > config files, etc) this can be hammered in with "<master>/bin/rpm > --prefix=<master> ...". But forget this in general. After building, > packages are in 70% of the time dependent to their prefix (<master> or > <client> here). > > Hmmmm?! > Ralf S. Engelschall > [EMAIL PROTECTED] > www.engelschall.com > ______________________________________________________________________ > The OpenPKG Project www.openpkg.org > User Communication List [EMAIL PROTECTED] > ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
