Hi Maciej, We already talked about this case on IRC: the file /etc/opt/csw/ssl/openssl.cnf is provided by CSWopenssl-utils but it is registered as /etc/opt/csw/ssl/openssl.cnf.CSW in the pkgmap of the package as the real /etc/opt/csw/ssl/openssl.cnf is created at install time using the cswpreserveconf class. So it's indeed a false alarm as there is a package that provides this file (the package itself) and there will be no dangling symlink when the package is installed.
That can probably be fixed in a another way (but I am not sure I understood your proposition, is it about creating a custom class action script to handle the creation of the symlink /opt/csw/ssl/openssl.cnf -> /etc/opt/csw/ssl/openssl.cnf ?). But for now I have no problem overriding this check. Anyway your comment was still useful, it made me notice that the openssl 0.9.8 recipe should simply not contain anymore the directives that create the openssl-utils and libssl-dev packages, they are generated by the openssl 1.0.1 recipe (which contains the same override). Yann 2014-06-05 23:18 GMT+02:00 Maciej (Matchek) Bliziński <[email protected]>: > On Thu, Jun 5, 2014 at 9:22 PM, <[email protected]> wrote: > > +# False alert > > +CHECKPKG_OVERRIDES_CSWopenssl-utils += > file-needed-but-no-package-satisfies-it|/etc/opt/csw/ssl/openssl.cnf|CSWopenssl-utils|contains|symlink|/opt/csw/ssl/openssl.cnf|which|needs|the|target|file:|/etc/opt/csw/ssl/openssl.cnf > > Hm, I tend to think that there is some legitimacy to this alert. It's > not just a spurious false alert out of nowhere. After all, the package > does contain a dangling symlink, as far as pkgmap is concerned, that's > a fact. :-) > > Maybe the class action script should create the /opt/csw/etc symlinks? > That would keep all this logic in once place. > > Maciej >
