In the second case the version numbers can diverge. So it allows a little more independence between the two libs. The downside is that one has to keep track of which version of libxml to use for a particular version of libxslt. Not a big deal, really, but there it is nonetheless. Also, something to consider, for this last option, it would be possible to move the libxslt lib over to it's own Rubyforge project (which already exists actually). Maybe that's a better idea?
I'd vote a separate project. Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/libxml-devel
