Sean Scott wrote: >>> Also we often want our "mtst" users to install versions of the package >>> that are not putback to ON yet. How can a package that is built in a dev >>> ws be installed? I have not found the magic combination of >>> options/paths. IPS does not have to use http does it? >>> >>> For example how can a package that is available at this location be >>> installed on a target system? Must the publisher settings be modified or >>> can the path be specified just for one install? >>> >>> /net/hyper.sfbay/tank/ws/cy152378/clr/drop1/packages/sparc/nightly/repo.extra/pkg >>> >>> >> The publisher settings must be modified. > > OK, so what is the correct set of options to use to set the publisher > appropriately? All my attempts returned errors. I also was not sure how much > of the path should be used. For example is the above path ok or should it end > at "repo.extra", or "sparc", or something?
Unless you have fairly recent pkg5 bits, you'd need to run a depot pointing toward that location (pkg.depotd -d /net/hyper.sfbay/tank/ws/cy152378/clr/drop1/packages/sparc/nightly/repo.extra) Recent pkg bits (I think build 140 and above?) support file:// URIs in the client, and you should be able to specify file:///net/hyper.sfbay/tank/ws/cy152378/clr/drop1/packages/sparc/nightly/repo.extra as an package origin directly, though this may not be wise with NFS paths, as the code somewhat assumes access to the filesystem to be low-latency. -- Rich _______________________________________________ on-ips-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
