Hi All, I'm soliciting a recommendation for how to handle a bug with the old apache removal process.
If you install CSWapache2, you get CSWapache2, CSWapache2c, CSWapache2rt and CSWap2prefork. At this point, due to use of installf in the postinstall of CSWap2prefork, CSWap2prefork owns /opt/csw/apache2/sbin/httpd. If you now install CSWap2worker to get the httpd.worker mpm, You'll have CSWap2worker as the owner of sbin/httpd (postinstall script again), while the httpd.prefork binary lives at sbin/httpd.prefork and sbin/httpd.worker-save. Upon removal, CSWap2worker removes sbin/httpd since it is the registered owner, It then moves sbin/httpd.worker-save back to sbin/httpd to clean up after itself. Now, if you remove the rest of the apache2 stack, you get sbin/httpd left behind as it has no owner. When the new packages come along, alternatives balks at creating the symlinks required due to an existing binary...this is good, but leaves the wrong httpd in place. I suspect that the only good solution is a preinstall script for the new CSWapache2 that will do: HTTPD=$PKG_INSTALL_ROOT/opt/csw/apache2/sbin/httpd PKG_INSTALL_ROOT= [ -x "$HTTPD" ] && rm -f "$HTTPD" Anyone got a more creative idea for handling this? Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
