From owner-freebsd-ports@freebsd.org  Thu Mar  9 00:22:50 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D192ED0171F
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Thu,  9 Mar 2017 00:22:50 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2610:1c1:1:6074::16:84])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id B4DCE61A;
 Thu,  9 Mar 2017 00:22:50 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1354)
 id 07EE93801; Thu,  9 Mar 2017 00:22:50 +0000 (UTC)
To: bob@immure.com, fjwcash@gmail.com
Subject: Re: Best way to cause synth to ignore rebuilding of a port??
Cc: freebsd-ports@freebsd.org
In-Reply-To: <CAOjFWZ6RkG8EiP8gBn=rDReK04XOF_87oa57qd-7e=fy6JpLJw@mail.gmail.com>
Message-Id: <20170309002250.07EE93801@freefall.freebsd.org>
Date: Thu,  9 Mar 2017 00:22:50 +0000 (UTC)
From: jbeich@freebsd.org (Jan Beich)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Mar 2017 00:22:50 -0000

Freddie Cash <fjwcash@gmail.com> writes:

> On Wed, Mar 8, 2017 at 11:57 AM, Bob Willcox <bob@immure.com> wrote:
>
>> On Wed, Mar 08, 2017 at 10:40:11AM -0800, Freddie Cash wrote:
>> > On Wed, Mar 8, 2017 at 8:04 AM, Bob Willcox <bob@immure.com> wrote:
>> >
>> > > What is the best way to get synth to simply ignore certain ports when
>> > > running
>> > > the upgrade-system command with it? I would like for it to not upgrade
>> > > firefox
>> > > (don't want to lose my tab groups) so I'd rather that it not even consider
>> > > updating firefox again, at least not till some form of tab groups are again
>> > > supported.
>> > >
>> > > Note that I haven't tried ver 52 of firefox, but from what I've read it
>> > > sounds
>> > > like all plugins/addons other than flash are no longer supported.
>> > >
>> >
>> > Switch to the ESR version, and all NPAPI plugins will be enabled and
>> > supported until around May of next year.  :)
>> >
>> > Firefox 52    disables everything except Flash.
>> > Firefox 52ESR leaves everything enabled.
>> >
>> > https://bugzilla.mozilla.org/show_bug.cgi?id=1269807
>> > 
>>
>> Yeah, but isn't the ESR version relatively down-level WRT to version 51
>> that
>> I'm currently using? The Makefile in www/firefox-esr has a verison of
>> 45.8.0.
>>
>> Not anxious to go backwards on everything.
>>
> 52ESR was just released.  Give the ports maintainer time to get it into
> the tree.  :)  (Note, I don't have Firefox on FreeBSD at the moment so just
> going by what's released online, not what's available in the ports tree.)

What's the point of rushing into ESR 52 from stable ESR 45 ? If you didn't
notice comment 136 in upstream bug mentions a workaround for non-ESR channel.

www/firefox-esr switch can drag until 2017-06-13 when ESR 45 would reach EOL.