> Gary Mills wrote: > > I'm running snv_127, working my way through the > procedure > > to set up an AI server and install a client. I > built the slim_source, > > which creates svr4 packages, and then imported them > into a > > local repository. [..] > > Now, `installadm create-service' worked, but it > reported this > > error: > > > > /usr/lib/installadm/setup-image[294]: > /usr/apache2/2.2/bin/apachectl: not found [No such > file or directory] > > > > I had to install the apache-2.2 package and clear > the SMF > > service to get past this one. Is a dependancy > missing from > > my IPS package? > > Yes, you have items missing from your package > manifest, you can sort > this out a bit by comparing with the manifest in the > dev repository: > > http://pkg.opensolaris.org/dev/manifest/0/SUNWinstalla > dm-tools%400.5.11%2C5.11-0.127%3A20091111T075012Z > > The additional manual dependency for SUNWapch22 and > the actuator tag > that causes automatic importing of the manifest are > both added as part > of the import processing done for each build.
Does this mean that a simple `pkgsend import' is not going to work completely for a svr4 package? How do you keep track of dependancies and actions in this case? Through trial and error I found several other dependancies: SUNWauto-install-common SUNWdhcs SUNWpython-lxml . My task was ultimately successful, but I was disappointed to discover how difficult it was to set up a development environment. -- This message posted from opensolaris.org
