but it doesn't complain about class(manifest) - so I guess once the spec goes to /dev or /release (and /contrib I hope) then a proper action is automatically addedd as Danek described.
imho it should be implemented in pkgbuild as it would simplify testing. On Wed, 6 May 2009, Andras Barna wrote:
this is not supported by pkgbuild pkgbuild knows only the basic actions like: file, directory, dependencies, legacy, etc On Wed, May 6, 2009 at 6:19 PM, Robert Milkowski <[email protected]> wrote:Hi, I built a package with pkgtool with SMF manifest inside. It gets built and installed properly but SMF service does not import automatically during package installation. If I import it manually then it is fine. In a spec file I do: #Install manifest %define svcdir /var/svc/manifest/application/proxy mkdir -p "${RPM_BUILD_ROOT}/%{svcdir}" cp "%{SOURCE1}" "${RPM_BUILD_ROOT}/%{svcdir}/%{name}.xml" %if %(test -f /usr/sadm/install/scripts/i.manifest && echo 0 || echo 1) %iclass manifest -f i.manifest %endif %dir %attr (0755, root, bin) %{svcdir} %class(manifest) %attr (0444, root, sys) %{svcdir}/* You can see the full spec at http://jucr.opensolaris.org/review/packages/472 -- Robert Milkowski http://milek.blogspot.com _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss-- Andy http://blog.sartek.net _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
