On Tue, Dec 28, 2004, Adam Engel wrote: > [...] I am attempting to build rpms on a 9.0 system and install them > on a Redhat 7.1 system. [...] > OpenPKG creates binary RPMs for the OS and architecture you run the build on. Installing binaries to a different OS or architecture is not recommended and might not work at all. If you believe or know it will work you can convince "openpkg rpm -Uvh" to give it a try by appending the --ignoreos and/or --ignorearch switches.
As Doug Summers pointed out chances to reuse binaries are better when doing the build on an old system and reuse on a later system because the latter might be binary backwards compatible (might require some "compat" OS packages). If you can afford it in terms of time, CPU horsepower and disk space it is recommended to build from source RPMs anyway, see FAQ [1]. > It is my understanding that if an admin needs to run a command, say ssh > <server>, he would need to do openpkg ssh <server> [...] > No, use "openpkg --help" to find out which OpenPKG specific commands exists. These are used to manage OpenPKG. The "payload" commands from packages like "ssh" can be accessed by executing them directly. Ensure to use the full path or modify PATH to point to the OpenPKG directories. OpenPKG can help setting up the shell environment as described in the tutorial [2]. [1] http://www.openpkg.org/faq.html#source-focus [2] http://www.openpkg.org/tutorial.html below "Fine tuning" -- [EMAIL PROTECTED], Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [email protected]
