Hello, I'd like to offer to maintain mail-client/squirrelmail. I still use it on a daily basis so would like it to remain in Portage. I suspect that maintaining it as a proxy maintainer is the correct approach to do this. I think the current big issue to fix is CVE-2017-7692 [1] which has been fixed upstream [2]. [1] https://bugs.gentoo.org/show_bug.cgi?id=616700 [2] https://sourceforge.net/p/squirrelmail/code/14650/
(In reply to Luke Bratch from comment #0) > Hello, I'd like to offer to maintain mail-client/squirrelmail. I still use > it on a daily basis so would like it to remain in Portage. > > I suspect that maintaining it as a proxy maintainer is the correct approach > to do this. > > I think the current big issue to fix is CVE-2017-7692 [1] which has been > fixed upstream [2]. > > [1] https://bugs.gentoo.org/show_bug.cgi?id=616700 > [2] https://sourceforge.net/p/squirrelmail/code/14650/ I will warn you that another major problem is PHP 7 compliance. This project needs lots of work before PHP 5.6 exits in roughly 2 years.
(In reply to Brian Evans from comment #1) > I will warn you that another major problem is PHP 7 compliance. This project > needs lots of work before PHP 5.6 exits in roughly 2 years. Agreed, this is a scary challenge but I'll see what can be done (that is, if upstream doesn't do the necessary work)!
Was anything actually done here? Good will won't keep this package around.
Created attachment 480616 [details] First attempt at new SquirrelMail ebuild Please find my first attempt attached. It uses a snapshot from the SquirrelMail project's daily snapshot page [1] and has fixes in the ebuild to try to address QA concerns by adding die to any external calls and changing the src_unpack section to use "if use foo; then" rather than "use foo &&". [1] http://snapshots.squirrelmail.org/
The versions on the web site have supported PHP 8 for over a year now. I don't understand why they don't make a release and bump the version number, but they want everyone to use the latest snapshot. Anyway, it would still be convenient to have this is portage, though I moved over to roundcube. The ebuild here needs to have the EAPI updated.
