Re: firefox
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-us...@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
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PHP version retirement
> Am 13.08.2019 um 08:13 schrieb @lbutlr : > > On 12 Aug 19, at 01:04 , Martin Waschbüsch wrote: >> So, I find it wrong to say, as I understood you, to remove a package from >> the ports tree because otherwise others people, for instance users of >> FreeBSD, would have the *expectation* of receiving support for those >> packages. > > There is not expectation that any code is being maintained, but there *IS* an > expectation that the software in ports is being maintained, supported, and is > functional. Agreed. But in which areas would you expect there to be problems for a package that was working up date x, got security and bug fixes until date x and the actual source code of which will not change after date x? The only things that come to my mind are changes in packages it depends on or changes in the base os. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PHP version retirement
On 12 Aug 19, at 01:04 , Martin Waschbüsch wrote: > So, I find it wrong to say, as I understood you, to remove a package from the > ports tree because otherwise others people, for instance users of FreeBSD, > would have the *expectation* of receiving support for those packages. There is not expectation that any code is being maintained, but there *IS* an expectation that the software in ports is being maintained, supported, and is functional. -- Im finding's you'r mis'use of apostrophe's disturbing. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
