Bug#844240: Intent to not ship squirrelmail with stretch
On Mon, November 28, 2016 13:56, Scott Kitterman wrote: > On Sun, 13 Nov 2016 18:31:48 +0100 Thijs Kinkhorst > wrote: >> Package: squirrelmail >> Severity: serious >> >> SquirrelMail has been missing from Stretch for a while now and I intend >> to leave it that way. This bug is to document this explicit choice (and >> room for any concerns). >> >> Upstream (of which I'm, at least on paper) part, has not made any new >> release of SquirrelMail since 2011. There is some activity in commits >> being done, but these do not result in releases. >> >> I've tried to work around this temporarily by packaging a snapshot of >> upstream svn, but I'm not happy with that since this is an arbitrary >> point in development and not a clear and tested release which we should >> ship and support for years. Popcon for squirrelmail is significant but >> shows a steady decline since 2010. >> >> Alternatives are availbale. There's the competing product roundcube >> which is actively maintained in Debian and shows a steady popcon >> increase. Another alternative is to install SquirrelMail from source >> which is very easy and makes it easier to e.g. keep up with commits or >> newer snapshots. The added value of a Debian package for squirrelmail is >> hence not immense in my opinion. >> >> Of course this is not to pass any judgement value or to try to >> discourage others from working on this package. I welcome any thoughts >> in this bug report, or interest in putting the work into a sustainable >> Debian package of squirrelmail. > > Squirrelmail is one of the blockers to php5 removal (See #846069). Please > comment on that bug about how we can keep squirrelmail, but still get rid > of php5 (personally, I don't see how). If PHP 5 is gone I see no reason to keep squirrelmail in unstable in its current form. So we should remove it (as per #846069). Cheers, Thijs
Bug#844240: Intent to not ship squirrelmail with stretch
On Sun, 13 Nov 2016 18:31:48 +0100 Thijs Kinkhorst wrote: > Package: squirrelmail > Severity: serious > > SquirrelMail has been missing from Stretch for a while now and I intend > to leave it that way. This bug is to document this explicit choice (and > room for any concerns). > > Upstream (of which I'm, at least on paper) part, has not made any new > release of SquirrelMail since 2011. There is some activity in commits > being done, but these do not result in releases. > > I've tried to work around this temporarily by packaging a snapshot of > upstream svn, but I'm not happy with that since this is an arbitrary > point in development and not a clear and tested release which we should > ship and support for years. Popcon for squirrelmail is significant but > shows a steady decline since 2010. > > Alternatives are availbale. There's the competing product roundcube > which is actively maintained in Debian and shows a steady popcon > increase. Another alternative is to install SquirrelMail from source > which is very easy and makes it easier to e.g. keep up with commits or > newer snapshots. The added value of a Debian package for squirrelmail is > hence not immense in my opinion. > > Of course this is not to pass any judgement value or to try to > discourage others from working on this package. I welcome any thoughts > in this bug report, or interest in putting the work into a sustainable > Debian package of squirrelmail. Squirrelmail is one of the blockers to php5 removal (See #846069). Please comment on that bug about how we can keep squirrelmail, but still get rid of php5 (personally, I don't see how). Scott K
Bug#844240: Intent to not ship squirrelmail with stretch
Package: squirrelmail Severity: serious SquirrelMail has been missing from Stretch for a while now and I intend to leave it that way. This bug is to document this explicit choice (and room for any concerns). Upstream (of which I'm, at least on paper) part, has not made any new release of SquirrelMail since 2011. There is some activity in commits being done, but these do not result in releases. I've tried to work around this temporarily by packaging a snapshot of upstream svn, but I'm not happy with that since this is an arbitrary point in development and not a clear and tested release which we should ship and support for years. Popcon for squirrelmail is significant but shows a steady decline since 2010. Alternatives are availbale. There's the competing product roundcube which is actively maintained in Debian and shows a steady popcon increase. Another alternative is to install SquirrelMail from source which is very easy and makes it easier to e.g. keep up with commits or newer snapshots. The added value of a Debian package for squirrelmail is hence not immense in my opinion. Of course this is not to pass any judgement value or to try to discourage others from working on this package. I welcome any thoughts in this bug report, or interest in putting the work into a sustainable Debian package of squirrelmail. Cheers, Thijs
