Hi again, I received no replies to yesterday's post. I an rephrasing my question below hoping that it would be easier to answer this way.
Here is my situation: 1) I have a bunch of precompiled binaries in /opt/$arch/app abd a few config files in /opt/$arch/app/conf. 2) The aim is to package these binaries using openpkg and add in configuration scripts for the files in /opt/$arch/app/conf. 3) I do not want to install the final application under /cw (or whereever the openpkg subtree is) but under /opt 4) The app will be deployed on 400 machines running Solaris and FreeBSD. Questions: A) After reading through the docs I am not sure if using Openpkg for the above job is a good idea or not. B) Can I provide a --prefix option to openpkg to install the binary in some location other than the installroot ? C) I don't understand the need for the rc file in case I am able to use the --prefix option (and I use the /full/path/to when i run openpkg) Any replies will be appreciated. Thanks, -ansh -----Original Message----- From: Anshuman Kanwar [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 04, 2003 11:57 AM To: '[EMAIL PROTECTED]' Subject: Trying to understand openpkg installroot Hi all, I've read through the handbook and other docs on the openpkg site. From what I understand, openpkg will install all packages under its own installroot ? Is this true ? Is there a way to install these packages in the system path ? I want to build my own packages on one machine and deliver on a fleet of 400 identical machines. In essence I just want a package delivery system ... the default openpkg way seems too intrusive. Could someone explain why openpkg needs to maintain its own self contained subtree ? Thanks, -ansh ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED] ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
