firefox

[Thomas Mueller]

bruce writes:

>  I used seamonkey for years without problems.  Now with seamonkey no
>  longer available I have tried firefox.  It crashes regularly and
>  isn't nearly as good as seamonkey.  When are you bringing seamonkey
>  back?

Robert Huff responded:

        Short answer: probably never.
        Longer answer:
        1) it is (I believe) no longer developed/maintained upstream.
        2) the port does not have a local maintainer.
        3) it has a long list of security issues, which persisted for
                months if not years.
        
        I, too, will miss it.  But in the larger scheme of things this probably the path of wisdom.

        (Now ... if you are volunteering to revive it, assume maintainership, and contribute patches - thankyouthankyouthankyou!!!!)
        
I went to www.seamonkey-project.org last night.  Seamonkey looked alive, but last update was over a year ago (July 27, 2019 as I best remember): 2.49.4 .

I looked in FreeBSD ports tree, which I track using svn: www/seamonkey was not there.

But www/seamonkey is still in (NetBSD) pkgsrc.

>From the Makefile, it looks like there is no maintainer:

DISTNAME=       seamonkey-${SM_VER}.source
PKGNAME=        seamonkey-${SM_VER:S/b/beta/}
PKGREVISION=    13
SM_VER=         2.49.4
CATEGORIES=     www
MASTER_SITES=   ${MASTER_SITE_MOZILLA:=seamonkey/releases/${SM_VER}/source/}
EXTRACT_SUFX=   .tar.xz

MAINTAINER=     pkgsrc-users at NetBSD.org
HOMEPAGE=       http://www.seamonkey-project.org/
COMMENT=        Full-featured gecko-based browser

One suggestion from me is www/otter-browser, available in FreeBSD ports, NetBSD pkgsrc, Linux (various), and haikuports (for Haiku).

Tom