On Thu, Jan 08, 2004, Christopher Chan wrote:
> I get the following error when trying to relocate openpkg's initial
> bootstrap install using the --prefix=/opt/myopenpkg, even though the
> default built prefix is /opt/spikesource.
>
> ./openpkg-20031228-20031228.ix86-redhat9-os.sh --prefix=/opt/spike
> OpenPKG CURRENT Binary Bootstrap Package, version 20031228
> Built for prefix /opt/spike on target platform ix86-redhat9
> ++ hooking OpenPKG instance into system environment
> ++ fixating OpenPKG instance root directory "/opt/spike"
> ++ extracting OpenPKG binary distribution
> ++ installing OpenPKG binary distribution
> ++ fixating OpenPKG instance filesystem hierarchy
> error: Unable to open /opt/spikesource/etc/openpkg/rpmrc for reading: No such
> file or directory.
> ./openpkg-20031228-20031228.ix86-redhat9-os.sh: /opt/spike/lib/openpkg/rpmtool:
> /opt/spikesource/lib/openpkg/bash: bad interpreter: No such file or directory
>
> Is this functionality suppose to work? and will all my subsequent rpm installs
> using openpkg rpms put the install under the new prefix???
Hmmm... yes and no. It is certainly a bug that the errors occur if you
install the bootstrap into a forced different prefix. But the --prefix
on the _binary_ .sh file is _NOT_ intended to _install_ the OpenPKG
instance under an arbitrary prefix for use. It is mainly provided for
debugging to be able to unpack the stuff into a temporary location
only. If you want to install into /opt/spike, you _HAVE_ to build
the bootstrap from the .src.sh by specifying the --prefix=/opt/spike
already there. Sorry if the existing --prefix on the binary .sh file is
confusing.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
