On Fri, Apr 22, 2005, Matthias Kurz wrote: > I have one build host for every platform/release. There the packages > are compiled from sources, leading to binary packages under RPM/PKG. In > this RPM/PKG i run "openpkg index" and it is mounted inside a hierarchy > that is accessible over anonymous ftp. From there the "slave" machines > get their binary packages.
My setup is similar, but after creating a new binary package on the build host there is an additional, manual and explicit step to "release" the new binary RPM. This means moving it to another directory where it is hooked into a webserver via a cgi script so that consumer hosts can install via rpm -Uvh http://.... . The "release" step also offers to remove likewise named RPMs from the publish directory (it does not do that automatically as there could be reasons to keep an "older" binary RPM for some time). This all is done with homebrew scripting and not supported by openpkg-tools features. Christian -- Christian Reiber, [EMAIL PROTECTED] ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [email protected]
