From owner-freebsd-ports@FreeBSD.ORG  Wed Sep 11 21:29:27 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id EC7BAE5D
 for <freebsd-ports@freebsd.org>; Wed, 11 Sep 2013 21:29:27 +0000 (UTC)
 (envelope-from mueller6721@twc.com)
Received: from cdptpa-oedge-vip.email.rr.com
 (cdptpa-outbound-snat.email.rr.com [107.14.166.225])
 by mx1.freebsd.org (Postfix) with ESMTP id B232329DD
 for <freebsd-ports@freebsd.org>; Wed, 11 Sep 2013 21:29:27 +0000 (UTC)
Received: from [74.130.200.176] ([74.130.200.176:18842] helo=localhost)
 by cdptpa-oedge03 (envelope-from <mueller6721@twc.com>)
 (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP
 id 20/C1-05277-5FFD0325; Wed, 11 Sep 2013 21:26:13 +0000
Date: Wed, 11 Sep 2013 21:26:13 +0000
Message-ID: <20.C1.05277.5FFD0325@cdptpa-oedge03>
From: "Thomas Mueller" <mueller6724@bellsouth.net>
To: freebsd-ports@freebsd.org
Subject: Re: What is MAKE_JOBS_UNSAFE?
X-RR-Connecting-IP: 107.14.168.142:25
X-Cloudmark-Score: 0
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2013 21:29:28 -0000

> > In most cases MAKE_JOBS_UNSAFE=yes will not help.  The message is an
> artifact from when the defaults were reversed and a precaution for the
> days after it was changed.

> IMHO it should be removed now.
        

> Eitan Adler

I'm inclined to agree with you.

I guess my best choice on what to do about gio-fam-backend and multimedia/vlc is
pkg delete vlc
pkg delete gio-fam-backend        

or

pkg delete -f gio-fam-backend

and let multimedia/vlc "sink or swim" for the time being, so I can go to the next step

portmaster -a -x multimedia/vlc

and then do multimedia/vlc later.

I think multimedia/vlc gets fairly frequent updates, so I won't have to wait too long.

It is possible that vlc functionality won't be impaired by having gio-fam-backend taken out from under.

I have to remember FreeBSD 9.2-RELEASE may be in the very near future.

Tom