On Fri, Oct 26, 2007, J P wrote: [...] > My question is that once we create a "unique" installation script for each > set of servers will we be able to safely reuse the same binary RPM files > that were originally created under the /export/home/tambu/openpkg directory? > Or do we have to recompile everything including all the perl modules? [...]
It's not a trivial job to relocate software which used to run under path /foo/bar/ to make it work under a different path /quux/. This problem is not specific to OpenPKG but applies to software in general as you will find hard coded file system path in almost every single binary and library which does things with certain complexity. Just think of config files, log files, load DSOs, etc. Therefore it is by far not sufficient just to hack to OpenPKG bootstrap script. Packages must be built under to same path as they are supposed to run. If you build OpenPKG packages on machine A with file system prefix /foo/bar/ you also have to supply this path on machine B. What you can do on machine B is to add additional access paths, e.g. using symlinks (/quux/ pointing to /foo/bar/) or provide loopback mounts which make /foo/bar/ accessable under mount point /quux/. On Solaris, this can be done using lofs(7FS), on FreeBSD see mount_nullfs(8), on NetBSD see mount_null(8), on Linux lookup the mount option "bind" in mount(8). On case of Solaris 10 and OpenSolaris be aware, that currently there is a problem using loopback mounts in /etc/vfstab when it comes to ZFS file systems [1]. [1] http://bugs.opensolaris.org/view_bug.do;jsessionid=bed98a9efedeafffffffff02e3d2be6e7ca4?bug_id=6464201 -cs ______________________________________________________________________ OpenPKG http://openpkg.org User Communication List [email protected]
