Stijn De Weirdt <[EMAIL PROTECTED]> writes: > hi all, > > i just installed openpkg on scientific linux 3, which is a clone of rhel3. > so i used > sh openpkg-2.4.0-2.4.0.ix86-rhel3-openpkg.sh --prefix=/opt/openpkg > to install openpkg. > the result was: > > OpenPKG 2.4-RELEASE Binary Bootstrap Package, version 2.4.0 > Built for prefix /opt/openpkg on target platform ix86-rhel3 > ++ hooking OpenPKG instance into system environment > ++ creating OpenPKG instance root directory "/opt/openpkg" > ++ extracting OpenPKG binary distribution > ++ installing OpenPKG binary distribution > ++ fixating OpenPKG instance filesystem hierarchy > openpkg-2.4.0-2.4.0.ix86-rhel3-openpkg.sh: /opt/openpkg/bin/openpkg: > /openpkg/lib/openpkg/bash: bad interpreter: No such file or directory > ++ post-processing OpenPKG bootstrap installation > openpkg-2.4.0-2.4.0.ix86-rhel3-openpkg.sh: > /opt/openpkg/lib/openpkg/rpmdb: /openpkg/lib/openpkg/bash: bad > interpreter: No such file or directory > openpkg-2.4.0-2.4.0.ix86-rhel3-openpkg.sh: > /opt/openpkg/lib/openpkg/rpmtool: /openpkg/lib/openpkg/bash: bad > interpreter: No such file or directory > > as you can see, some of the install scripts look for bash in the > default /openpkg/lib/openpkg/bash instead of the prefixed one. a > simple symlink ln -s /opt/openpkg/ /openpkg and a rerun apparently > fixed the issue.
I'm not sure but I don't think you can change the build in prefix once you have defined it. I think that you must rebuild the binary shell script using the appropriate --prefix option from the openpkg-2.4.0-2.4.0.sh script. Whether that is right or not it might be handy to have this explicitly mentioned in the handbook as I think I got similary caught out with this before. Simon ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List openpkg-users@openpkg.org
