Update of the docbook-xsl-stylesheets ebuild to the latest version.
Created attachment 5662 [details] docbook-xsl-stylesheets-1.57.0.ebuild
This ebuild follows the practice of the previous ebuild, using SLOT="0" and overwriting /etc/xml/catalog. However, I do not agree with this approach. There is nothing wrong with having different versions of the Docbook stylesheets installed. In fact, a user who works with lots of Docbook documents may even require older versions. Thus I would suggest that we begin installing each new release of the Docbook stylesheets in a separate SLOT, and modify the ebuilds to simply add their entries to /etc/xml/catalog rather than overwriting it.
Ok, just a quick question - what are the changes made between versions for XSL stylesheets? Bug fixes, that sort of thing? Or major changes? If we see primarily bugfixes, then I think it might actually end up being far easier to keep track of installation for compatible stylesheets by updating the whole installation and leaving SLOT="0". In the past, having multiple entries of SGML has crippled some users' installations by preventing installation of ANYTHING that relied on docbook. Can it be guaranteed that this wouldn't happen if we change slot on the XSL stylesheets?
Looking over the changelog for the docbook stylesheets, it does seem like the changes are mostly bugfixes. So maybe sticking with SLOT=0 is the right thing to do. However, overwriting /etc/xml/catalog still seems bad: other packages could be writing to this file as well, right? Instead maybe it should use xmlcatalog --del to remove any old docbook XSL entries.
Ok, I've started taking a look at this. I'm going to have to change things around a bit, fixing up the postrm stuff so that it doesn't just blindly delete the xmlcatalog... Indeed, yes, other packages DO write to that file. Ugh, this needs to be fixed, and I'll have to bump the portrevision, I think.
Ok, what I've done is hardcoded a remove of 1.52.2, which I didn't particularly want to do, but it seems to be the only way. From here on out, the package will clean up after itself... I'm committing the new ebuild.
