on 08/02/2012 03:20 Doug Barton said the following: > On 02/07/2012 02:49, Andriy Gapon wrote: >> >> I would like to ask you to review and test the port in this PR: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=164843 > > Using the latest shar on up to date 8-stable i386 it seems to run fine. > FWIW I'm using the port with all of the OPTIONS UNchecked. > > A couple of notes: > > * There is a man page listed in the Makefile, but it doesn't seem to exist.
Weird. It definitely exists in the source code and here it even gets installed: $ pkg_info -W /usr/local/man/man1/xfreerdp.1.gz /usr/local/man/man1/xfreerdp.1.gz was installed by package freerdp-1.0.0 BTW, the content of this manual seems to be a bit outdated. There used to be a better manual page online at this location: http://www.freerdp.com/wiki/doku.php?id=documentation:userdocs:xfreerdp_manpage but now it seems to be gone. But google cache has it for time being: http://webcache.googleusercontent.com/search?q=cache:Mgy8LqzGuZEJ:www.freerdp.com/wiki/doku.php%3Fid%3Ddocumentation:userdocs:xfreerdp_manpage+&cd=2&hl=en&ct=clnk&lr=lang_en|lang_uk&client=firefox-a > * When I exit I get this: Failed to check xfreerdp file descriptor I've seen this message too. Maybe it's something worth reporting upstream. >> I also would to discuss with the port's users the best approach to updating >> it. > > Given that I use this daily for $WORK and am heavily dependent on it, I > really appreciate you asking this question. :) My suggestion is that > once you're confident that it is effective as a superset of the old > version then go ahead and update the port. If it turns out that people > have trouble with the new version that cannot be addressed in a timely > manner you can always proceed with adding the -legacy port that you > mentioned in your PR. It seems that this version works fine for, but I am not sure about the complete compatibility. Actually, I seem to experience some problem with embedding freerdp window inside another application using -X option. I wonder if anyone else uses that option and can report how it works. > One word of caution for those (like me) who have a button or other > mechanism to start it from your DE, and are connecting to something > that's SSL protected. Start it on the command line first, so that you > can answer the dialog about accepting the SSL certificate. I filled a 2G > /var/log in less than a minute before I realized why the thing hadn't > popped up a window yet. Good advice. I also had to use --no-nla option to get freerdp working the way it did before. BTW, just in case, just noticed this page referenced from the freerdp's main page: http://remmina.sourceforge.net/ Looks like a potentially useful software. -- Andriy Gapon _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
