Ingo, I have written a helper script for managing my local openpkg repository: openpkg-mgr. It is attached. I has a few hard-coded items for our environment but it should be pretty easy to adapt to other locations. The script supports the following workflow:
1. openpkg-mgr trial - Interactively get new source rpms (and build) using openpkg build (with caching filter). The source rpms are cached to a temporary location. 2. openpkg-mgr release - Install new source rpms in /netgenics/openpkg-src. 3. Edit the build spec for each platform - I generate them from another config file and distribute with cfengine ... this one is up to you. 4. openpkg-mgr build - When the build file is released the packages will be built on all specified platforms and installed in /netgenics/openpkg-rpm by periodic jobs on the build servers. 5. openpkg-mgr update - End servers update all their binary rpms by periodically running "openpkg-mgr update -a". New packages can be installed by specifying the desired package name instead of the "-a" option. Martin ---- Martin Andrews [EMAIL PROTECTED] > -----Original Message----- > From: Ingo T. Storm [mailto:[EMAIL PROTECTED] > Sent: Monday, March 03, 2003 7:13 AM > To: [EMAIL PROTECTED] > Subject: correct use of openpkg-tool? > > > As said before, I am trying to create a central build server for > OpenPKG 1.2 that is meant to serve binary RPMs. The clients will be a > bunch of Suns running Solaris 9 and should alert me if there are > updates for rpms they have installed. > > If anyone has an infrastructure in place that does this, please speak > up!
openpkg-mgr
Description: Binary data
