Hello Joseph, Hey that's great. I just wrote 'yipee, it works' in the Handbook for version 1.1. If you need help with your package building just ask. If you need immediate help, the only documentation dealing with package building is the Handbook http://www.openpkg.org/doc/handbook/openpkg.html.
OpenPKG will install a package only to its own hierarchy, and that is what lets it securely offer the big advantage of multiple OpenPKG instances on one machine. For example, if you bootstrap to the directory /cw and then install a package with the command /cw/bin/rpm -Uvh, the package contents will be installed only to the subdirectories of /cw (usually /cw/bin /cw/lib and so on.) If you have a second OpenPKG instance and have bootstrapped it to /sfw, then running /sfw/bin/rpm -Uvh will install to a subdirectory of /sfw. You see where this is going. By the way, when I mentioned the small section in the Quick Reference regarding 'Preparing the environment', I meant that if you have multiple instances of OpenPKG it is useful to run "eval `/cw/etc/rc --eval all env`" or something like that. A run-command script will then begin setting your environment variables so that you can just type rpm -bb, rpm --rebuild, rpm -Uvh, and so on, knowing that the correct OpenPKG instance will be used. Check this out. Good luck, Michael -- [EMAIL PROTECTED] Development Team, Application Services Cable & Wireless Deutschland GmbH On Thu, Apr 04, 2002 at 02:16:18AM +1000, Joseph Sirucka wrote: > Michael > > Make note to mention this on the documentation. > > It works yipee. > > now I gonna make some openpkgs hopefully without questions being asked. > > Also when I make packages do they have to reside under the /cw > directory, or can they reside under the main filesystem. > > A happy camper. > > Joseph ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
