Simon, This works in 2.0. 2.1 may be a little different. You have to install these in this order on all machines to get the 'build' tool working:
openpkg make binutils gcc perl openpkg-tools If you have a lot of servers, you may want to have just one server compile them, then put the binary packages on an NFS share for the others to install from. This helps solve a chicken and egg problem of compiling the compiling before your sandbox is ready. For solaris, I had to grab the sunfreeware.com's binary gcc to get my build host bootstrapped. If you installed the development stuff with Solaris, you may not have to do this. Once that is done, you can then run commands like: /opkg/bin/openpkg build ntp | /bin/sh - This will automagically find, build, and install ntp and its package dependencies in the proper order. Its somewhere in between a Mandrake urpmi and gentoo's emerge IMO. Again, if you have a lot of servers, you will want to rsync nightly against the openpkg servers and then run your build commands against a local mirror. It is much faster this way and saves bandwidth for C&W. The mirror command I use in cron is: 0 0 * * * /opkg/bin/rsync -azv --exclude "BIN/" --exclude "ISO/" rsync://rsync.openpkg.org/openpkg-ftp/release/2.0/ /mirror/release/2.0/ If you have custom packages and need to rebuild your index then you can cron this as well: 0 4 * * * /opkg/bin/openpkg index -c -r OpenPKG-2.0/Source/ -o /mirror/release/2.0/SRC/00INDEX.rdf.bz2 -i /mirror/release/2.0/SRC/ After you have your mirror setup, the build command above changes to: /opkg/bin/openpkg build -f ftp://<your server name>/release/2.0/00INDEX.rdf ntp | /bin/sh - You obviously also need to setup anonymous ftp on the mirror server. I know it took me some time to figure these steps out so hopefully this will help you. Aaron On Wed, 2004-07-21 at 14:05, Simon J Mudd wrote: > Hi, > > I've been looking at OpenPkg now for several days and like what I see, > but > I seem to be missing somethings: > > I'm using Whitebox Linux (a RedHat Enterprise 3 clone) which isn't > supported. What could I do to the bootstrap procedure to convince > openpkg > I'm using RHEL3 so I can just download the prebuilt packages? Any > pointers? > > 2. After building and executing > openpkg-2.1.0-2.1.0.ix86-whitebox3.0-ope.sh I can setup the opa > environment and see the basic openpkg commands. > > - I can download the src rpms. > - I can build them > - I can install them > > However this whole process is manual and you need to know all the > package > building dependencies to get the "interesting" rpms installed. This > is > slow, error prone and time consuming. > > I've since seen that there is openpkg-index and openpkg-build which > appears to be a tool to allow me to build (and install?) updated > packages > immediately. Is that so and is it documented? If not could someone > give > me some pointers as to what to setup so I can use it. > > I'd like to keep OpenPKG uptodate. Someone on this list suggested yum > to > do this (though it is not ported to openpkg) and I am unsure how this > should be done or if it can be done "reasonably" automatically using > OpenPKG tools. Can someone clarify is this is possible? > > Sorry for the newbie questions. I'm think the whole OpenPkg idea is > very > nice. I'm unsure if the information I'm "missing" is "work in > progress" > or me not being able to find it. > > Thanks for any feedback. > > Regards, > > Simon > ______________________________________________________________________ > The OpenPKG Project www.openpkg.org > User Communication List [EMAIL PROTECTED] > ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
