[arch-dev-public] dropping FreeNX/OpenNX and nx-common
I'd like to drop FreeNX from our extra repo. It's not maintained for several years now though it can still do its job pretty well with some heavy patching and sed commands fixing things that have changed meanwhile. We've already dropped the closed NoMachine NX client and I'd like to drop OpenNX along with FreeNX because there's a successor out there named X2go. X2go packages are in extra: a functional replacement with the same and better features. And it's well maintained upstream. nx-common pkg with remaining NoMachine libs is only required by FreeNX and OpenNX and can be removed too then. Any objections or somebody who wants to take over these packages? -Andy
Am 24.06.2013 22:14, schrieb Andreas Radke:
I'd like to drop FreeNX from our extra repo. It's not maintained for several years now though it can still do its job pretty well with some heavy patching and sed commands fixing things that have changed meanwhile.
We've already dropped the closed NoMachine NX client and I'd like to drop OpenNX along with FreeNX because there's a successor out there named X2go.
X2go packages are in extra: a functional replacement with the same and better features. And it's well maintained upstream.
nx-common pkg with remaining NoMachine libs is only required by FreeNX and OpenNX and can be removed too then.
Any objections or somebody who wants to take over these packages?
-Andy +1 x2go works well.
-- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Am 27.06.2013 15:47, schrieb Tobias Powalowski:
Am 24.06.2013 22:14, schrieb Andreas Radke:
I'd like to drop FreeNX from our extra repo. It's not maintained for several years now though it can still do its job pretty well with some heavy patching and sed commands fixing things that have changed meanwhile.
We've already dropped the closed NoMachine NX client and I'd like to drop OpenNX along with FreeNX because there's a successor out there named X2go.
X2go packages are in extra: a functional replacement with the same and better features. And it's well maintained upstream.
nx-common pkg with remaining NoMachine libs is only required by FreeNX and OpenNX and can be removed too then.
Any objections or somebody who wants to take over these packages?
-Andy +1 x2go works well.
I've had lots of NX problems recently - is x2go really better, and is it easier to use?
Am 27.06.2013 15:49, schrieb Thomas Bächler:
Am 27.06.2013 15:47, schrieb Tobias Powalowski:
Am 24.06.2013 22:14, schrieb Andreas Radke:
I'd like to drop FreeNX from our extra repo. It's not maintained for several years now though it can still do its job pretty well with some heavy patching and sed commands fixing things that have changed meanwhile.
We've already dropped the closed NoMachine NX client and I'd like to drop OpenNX along with FreeNX because there's a successor out there named X2go.
X2go packages are in extra: a functional replacement with the same and better features. And it's well maintained upstream.
nx-common pkg with remaining NoMachine libs is only required by FreeNX and OpenNX and can be removed too then.
Any objections or somebody who wants to take over these packages?
-Andy +1 x2go works well. I've had lots of NX problems recently - is x2go really better, and is it easier to use?
I replaced it within 5 minutes. So migration was really easy. Look at the wiki. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
participants (3)
-
Andreas Radke
-
Thomas Bächler
-
Tobias Powalowski