Sonn,
Hmm, I thought I'd written up my findings somewhere but I can seem to find it now.
But the gist of what I was thinking is this:
1) For dropping PEAR/XML, which looks to be used for the xml_feed_parser on RSS feeds, we could try using PHP in-built XML_Parser / XMLREADER or similar
2) For dropping PEAR/Archive/Tar we could just make an executive decision and drop the ability to extract .tar/.tar.gz archives in the Files page, as I suspect very few people use this functionality.
As most systems now have some in-built form of zip/unzip available we could just alert them with a message saying if they want to extract the files from the archive they will need to add it as a valid .zip format. Or not even bother and just have some mention of it in the Mahara manual.
3) For dropping PEAR/Log - not sure for this but it would be good to find out what it is logging and why that is different to error_log/log_debug. It might be simply we can use one of those to achieve the same result.
Sonn,
Hmm, I thought I'd written up my findings somewhere but I can seem to find it now.
But the gist of what I was thinking is this:
1) For dropping PEAR/XML, which looks to be used for the xml_feed_parser on RSS feeds, we could try using PHP in-built XML_Parser / XMLREADER or similar
2) For dropping PEAR/Archive/Tar we could just make an executive decision and drop the ability to extract .tar/.tar.gz archives in the Files page, as I suspect very few people use this functionality.
As most systems now have some in-built form of zip/unzip available we could just alert them with a message saying if they want to extract the files from the archive they will need to add it as a valid .zip format. Or not even bother and just have some mention of it in the Mahara manual.
3) For dropping PEAR/Log - not sure for this but it would be good to find out what it is logging and why that is different to error_log/ log_debug. It might be simply we can use one of those to achieve the same result.
Robert