Yeah, while I haven't spent enough time in Haiku[0] to get familiar with really it's design language, it is so responsive, readable, and discoverable that it forced me to remember all that we have lost in personal computing because of... I'm not entirely sure who to blame, a lot of people who aught to be shot out of a cannon into the sun, I reckon.
[0] sadly it doesn't even quite meet my relatively minimal almost-never-used laptop use case due to the only RDP client that worked at all being so horrifically out of date that it can't understand modern RDP authentication mechanisms.
> the only RDP client that worked at all being so horrifically out of date that it can't understand modern RDP authentication mechanisms.
Do you mean rdesktop? Indeed it's pretty old and probably should be disabled, so I just did that.
Did FreeRDP not work, then? It seems we had a 3-year-old version, so I just spent the morning updating it to the very latest (2.4.1). Seems to work fine here for me, I connected to a remote Windows machine successfully. (The port is missing a bunch of features, but the basics seem to work.)
In the future you can report issues to HaikuPorts directly, or feel free to ping me on IRC/Matrix/XMPP.
Thanks, I will take a look when I get home. I was using rdesktop via BeRDP and on its own, but it choked on the auth portion. IIRC FreeRDP failed to launch. Also tried the KRDC port but it never gave me the option of using RDP despite its claims.
I was a little annoyed at the gigantic pile of packages that came along with those last two options, but there's no need to rehash rehash that argument. I do wish there had been an obvious way to clean those up after removing the applications they supported though.
FreeRDP is CLI-launch-only, so if you tried to start it via the GUI, that may have been your problem. We should probably rework BeRDP to use FreeRDP instead of rdesktop, but that's more involved.
I think KRDC may be hardcoded to use "xfreerdp", so it won't find the Haiku variant.
Yeah, "autoremove" isn't implemented unfortunately, nobody has gotten around to that yet. It would indeed be nice to have.
I was launching it via the CLI. As I said, I'm afraid I do not recall the reason it failed to launch. If it does so now that you have updated it I will forward what information I can through the appropriate channels.
