Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Mar 2013 17:19:19 +0900
From:      meta <meta@vmeta.jp>
To:        Ruslan Makhmatkhanov <cvs-src@yandex.ru>
Cc:        ports@freebsd.org
Subject:   Re: Status of net/freerdp and PR164843
Message-ID:  <8f22fb0026fc7736ed7c847b0c8ee921@vmeta.jp>
In-Reply-To: <5142CD9C.9020404@yandex.ru>
References:  <393b65ec29a67852a082f43dbe6a0673@vmeta.jp> <5142CD9C.9020404@yandex.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
For your information, I explain patches placed in files directory.
I hope this will help you.

files/patch-libfreerdp-*:
   Backport patches. The issues are fixed in recent master repo. But not 
included in 1.0.2 release.
   https://github.com/FreeRDP/FreeRDP/issues/536
   https://github.com/FreeRDP/FreeRDP/pull/544

files/patch-cmake_FindFFmpeg.cmake:
   To use multimedia/ffmpeg-devel instead of miltimedia/ffmpeg.

2013-03-15 16:28 Ruslan Makhmatkhanov wrote:
> Hi,
> 
> meta wrote on 15.03.2013 11:12:
>> Hey, who is responsible for net/freerdp?
>> I requested the maintainer to update freerdp on October via private
>> email but he does nothing.
>> I requested the new maintainer again Feb 27.
>> http://www.mail-archive.com/freebsd-ports@freebsd.org/msg47573.html
>> 
>> ports/164843 for freerdp 1.0.0 is open more than one year.
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=164843
>> 
>> As nobody works to update net/freerdp, I finally did it by myself.
>> 1.0.2 is available on my repository and tested on redports.
>> https://redports.org/browser/meta/net/freerdp
>> https://redports.org/buildarchive/20130312162341-90320/
>> 
>> WHOULD SOMEONE PLEASE WORK FOR IT?
> 
> Just grabbed it. Please send your patch as follow-up so we don't lose
> it in tracking history. Thank you.

-- 
`whois vmeta.jp | nkf -w`
meta <meta@vmeta.jp>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8f22fb0026fc7736ed7c847b0c8ee921>