Thanks Bart for your information and suggestions.
In fact, we are planning to support repository in our future releases. Thanks, Ervin. From: Bart Smaalders <[email protected]<mailto:[email protected]>> To: [email protected]<mailto:[email protected]> Subject: Re: [pkg-discuss] 'pkg install' performance issue Message-ID: <[email protected]<mailto:[email protected]>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 12/23/11 01:33, Ervin Yan wrote: > Hi, Shawn and Alan: > > Really appreciate for your replies. > > Since our customers may only need 4 of the packages for basic > functions, and need not download the whole image from our production > > server, and to provide consistent customer experiences with other > > platforms, we decided to use separate p5p file for different packages, > > like rpm file on Linux, and bff file on AIX. > Ok.... > > In fact, our own installer script can check the dependencies for our > product packages, and determine which packages need be installed or > > upgraded, or uninstalled. > Fine.. but you cannot check the OS packages. > > So I have one question, does 'pkg install' command have any options > that it can simply uncompress the p5p archive, install the package > files, > and skip to check dependencies, skip to check publisher > configurations? > No, because that would result in the machine being in an unsupportable state, with missing dependencies, etc. Right now, machines with zones cannot accept archive packages. This is a bug and is being fixed, but for now you need to create a local repository from the archive packages (say /tmp/a.p5p, /tmp/b.p5p), and add that to the publisher configuration. #create tmp repo pkgrepo create /tmp/mytmprepo # copy all the pkgs in /tmp/a.p5p into /tmp/mytmprepo pkgrecv -s /tmp/a.p5p -d /tmp/mytmprepo '*' # copy all the pkgs in /tmp/b.p5p into /tmp/mytmprepo pkgrecv -s /tmp/b.p5p -d /tmp/mytmprepo '*' # add temporary publisher pkg set-publisher -p /tmp/mytmprepo # install all packages from temp repo. .... In general, I strongly recommend that any ISV providing operating system components provide a external repo for their customers. It makes support much simpler, more elegant, and allows you to manage dependencies properly without having to have the customer download different packages, etc. This is particularly important if a new version of the ISV's software is needed for a new version of Solaris; by making packages for the new version of Solaris available in a repo that the customer can configure a seamless upgrade can be achieved. - Bart _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
