From owner-freebsd-ports@FreeBSD.ORG  Tue Oct  8 18:18:46 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id B21E7E01
 for <freebsd-ports@freebsd.org>; Tue,  8 Oct 2013 18:18:46 +0000 (UTC)
 (envelope-from rfg@tristatelogic.com)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 8C4E02606
 for <freebsd-ports@freebsd.org>; Tue,  8 Oct 2013 18:18:46 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id 7C5653AC97;
 Tue,  8 Oct 2013 11:18:41 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: Thomas Zander <thomas.e.zander@googlemail.com>
Subject: Re: FreeBSD mplayer port update?
In-Reply-To: <CAFU734xXW2A3k_Db1RAhdpDoUeupx6G1fM-q1tu78Jb6=y2-fg@mail.gmail.com>
Date: Tue, 08 Oct 2013 11:18:41 -0700
Message-ID: <59481.1381256321@server1.tristatelogic.com>
Cc: freebsd-ports@freebsd.org
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: Tue, 08 Oct 2013 18:18:46 -0000


In message <CAFU734xXW2A3k_Db1RAhdpDoUeupx6G1fM-q1tu78Jb6=y2-fg@mail.gmail.com>
, you wrote:

>On 8 October 2013 02:10, Ronald F. Guilmette <rfg@tristatelogic.com> wrote:
>
>> Could someone (anyone) explain to me why the FreeBSD port of mplayer
>> has not been updated at all since March 8th of this year?
>
>Yes.
>That is because I am preparing roughly 2 major updates per year,
>preferably shortly after a FreeBSD release. The other changes to the
>port are to maintain compatibility and fix whatever problems users may
>have.
>
>To pre-empt the inevitable question: Yes, there will be a new version
>before the end of October.
>Do you miss a specific feature in the current port or why do you press
>for an update?


The answer to your question is just this:

On very rare occasions, I come upon a video that does not seem to
play correctly (using mplayer).  When this happens, it may be the fault
of the video itself, or perhaps of mplayer.  If I knew that my mplayer
had been updated recently, then I would tend more to suspect the video
file of being corrupted.

And also, of course, even when videos play "correctly" I do often wonder
whether or not I am getting the full benefits of my hardware.