[aur-requests] [PRQ#2846] Deletion Request for nx-all
Chris_TR [1] filed a deletion request for nx-all [2]: The package has been outdated for a while and although it's not orphan, it hasn't been updated since it got adopted. Per the notice at the top of https://wiki.archlinux.org/index.php/FreeNX , it's not supported and it's been replaced by X2Go. [1] https://aur.archlinux.org/account/Chris_TR/ [2] https://aur.archlinux.org/pkgbase/nx-all/
Il 28 marzo 2015 02:01:10 CET, notify@aur.archlinux.org ha scritto:
Chris_TR [1] filed a deletion request for nx-all [2]:
The package has been outdated for a while and although it's not orphan, it hasn't been updated since it got adopted. Per the notice at the top of https://wiki.archlinux.org/index.php/FreeNX , it's not supported and it's been replaced by X2Go.
[1] https://aur.archlinux.org/account/Chris_TR/ [2] https://aur.archlinux.org/pkgbase/nx-all/
Why should it be deleted then? X2go cannot replace FreeNX, it's not compatible all in both sides http://wiki.x2go.org/doku.php/doc:faq:start FreeNX 4 is not the same of FreeNX 3 and cannot provide the same functionality, therefore until I find a valid reason to break compatibility with NX and with the wiki itself, I won't update FreeNX to v4. If you want I could submit a separated FreeNX v4 package. However I cannot find a single reason to delete the working nx-all package. -- Muflone
FreeNX 4 is not the same of FreeNX 3 and cannot provide the same functionality, therefore until I find a valid reason to break compatibility with NX and with the wiki itself, I won't update FreeNX to v4.
If you want I could submit a separated FreeNX v4 package. A better approach would be to create a separated package for older FreeNX 3 and update the nx-all package to v4 (if it works). -- Muflone
Actually, yeah, that sounds much better: have both packages, v3 and v4. Need any help with the v4 packaging? hk:v5sw4hw3pr6XMFck4edu6ln5/6ma4os6UedVcr4bo7ga4DBXCa32p/9+/8h7et6S On Sat, Mar 28, 2015 at 4:41 AM, Muflone <webreg@vbsimple.net> wrote:
FreeNX 4 is not the same of FreeNX 3 and cannot provide the same functionality, therefore until I find a valid reason to break compatibility with NX and with the wiki itself, I won't update FreeNX to v4.
If you want I could submit a separated FreeNX v4 package. A better approach would be to create a separated package for older FreeNX 3 and update the nx-all package to v4 (if it works). -- Muflone
Request #2846 has been rejected by Muflone [1]: https://lists.archlinux.org/pipermail/aur-requests/2015-March/005957.html [1] https://aur.archlinux.org/account/Muflone/
participants (3)
-
Chris T.R.
-
Muflone
-
notify＠aur.archlinux.org