Well, I love a challenge. Thanks for the info on package classes in current (I had seen the Junk tag but thought all the current packages had it). I guess I will pursue rt under the local tree first.
While I have your attention - I am a little uncertain about "rpm --makeproxy". My current homebrew package system lets me select per package/host whether I want the software locally installed or linked to an NFS volume. It looks like makeproxy will let me do that with openpkg. The only strange thing is that the links point to exactly the same openpkg tree - for example if my tree is /opt/openpkg then after installing the proxy gcc rpm into the tree the link for bin/gcc would point to /opt/openpkg/bin/gcc too - a circular link. I would want it to point to something like /automount/openpkg-sparc64-solaris2.9/bin/gcc. I see that all the links are indirect through a .prefix-gcc link - am I supposed to override that link after installing? The .prefix-gcc link does not appear to be tagged as a config file. Or is there another option to --makeproxy that specifies where the prefix link should point? The latter seems ideal to me. Martin ---- Martin Andrews [EMAIL PROTECTED] > -----Original Message----- > From: Ralf S. Engelschall [mailto:[EMAIL PROTECTED]] > Sent: Sunday, November 17, 2002 3:08 AM > To: [EMAIL PROTECTED] > Subject: Re: openpkg newbie trying to build rt from current > ... > > Outch, you performed the worst possible start with OpenPKG: > with a JUNK > package in OpenPKG-CURRENT. Sorry, this by definition has to mean that > you have to fail 100% :-( > > OpenPKG-CURRENT currently has the following packages (in decreasing > stability/completeness/etc order): > > class packages > ===== ======== > CORE 22 > BASE 149 > PLUS 106 > EVAL 121 > JUNK 10 > ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
