Date: Thu, 12 Jan 2012 13:20:46 -0500 From: Michael Scheidell <scheidell@freebsd.org> To: Thomas Zander <thomas.e.zander@googlemail.com> Cc: freebsd-ports-bugs@freebsd.org Subject: Re: ports/163969: [maintainer-update] mplayer and mencoder ports to a recent snapshot Message-ID: <4F0F247E.7090701@freebsd.org> In-Reply-To: <CAFU734xVoJ00z6aYmpBq_0bY5sYSpvDEWb-KjySUxTUbhq=pYA@mail.gmail.com> References: <201201111315.q0BDFoZ1097441@freefall.freebsd.org> <CAFU734xVoJ00z6aYmpBq_0bY5sYSpvDEWb-KjySUxTUbhq=pYA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/12/12 12:29 PM, Thomas Zander wrote:
>> #1 If some of the patches are already committed upstream, you would also need to change distfile, and maybe bump
>> portversion.
>> #2, the diffs on the Makefiles indicate you are not sending patch against current cvs Makefiles.
>> Can you update your ports tree, and resubmit the patch once you know what happened upstream?
> Okay, this is how it goes:
> #1: I _know_ what happened upstream because I _make_ that distfile
> (the mplayer developers don't do releases, this is left to the
> maintainers of the respective OS distribution) and put it on a server
> I have access to. Therefore distfile, PORTVERSION and PORTREVISION are
> perfectly alright. So is the rest of the port (at least there weren't
> any complaints when I called for testers on the ports mailing list, so
> I assume it worked for them too).
> #2: Done, attached.
understood.. tindering now.
(greets Martin...)
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
>*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F0F247E.7090701>