Did you see Packaging and Delivering Software with the Image Packaging System http://hub.opensolaris.org/bin/download/Project+pkg/files/ipsdevguide.pdf
On 05/15/12 00:43, Steve Christensen wrote:
1. Suppose I want to have packages that are x86 or SPARC only. How do I put the information into the package to make sure that someone wanting a SPARC install does not get an x86 one? So, for example, if I have a package for software foo-1.0 in SPARC and one in x86, do they have to be named differently or put on two separate servers? What are the rules? I do not want users to have to download a package that contains both.
page 41 - variant.arch
2. Now suppose I have a system where I want to install something on /opt/sfw, but the /opt/sfw directory does not have enough space and I make it a link to a place on a larger disk. In at least one attempt to install a package designed to go into /opt/sfw, I found that the package failed to install with a message that says /opt/sfw is a file or some such. Is there some IPS package option to avoid this or some other trick, or did I just do something wrong?
I suppose you looked at link actions. See pages 12 and 15. Also "Delivering Directories To Be Shared Across Boot Environments" on page 56. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
