[aur-general] community cleanup: removal of nextaw
Hello, this is a proposal to remove nextaw from community. It is not needed by any community package. It once was a dependency of siag-office, which has been moved to unsupported long ago and is still unmaintained there. Regards Stefan
On 06/12/2010 07:54 PM, Stefan Husmann wrote:
Hello,
this is a proposal to remove nextaw from community. It is not needed by any community package. It once was a dependency of siag-office, which has been moved to unsupported long ago and is still unmaintained there.
Regards Stefan
+1 -- Ionuț
On 06/12/2010 07:54 PM, Stefan Husmann wrote:
this is a proposal to remove nextaw from community. It is not needed by any community package. It once was a dependency of siag-office, which has been moved to unsupported long ago and is still unmaintained there.
I am not against removing, but as I understand http://siag.nu/neXtaw/usage.shtml nextaw is drop in replacement of libXaw. So all packages which depend on libxaw can be used with nextaw.
Am 12.06.2010 19:06, schrieb Sergej Pupykin:
On 06/12/2010 07:54 PM, Stefan Husmann wrote:
this is a proposal to remove nextaw from community. It is not needed by any community package. It once was a dependency of siag-office, which has been moved to unsupported long ago and is still unmaintained there.
I am not against removing, but as I understand http://siag.nu/neXtaw/usage.shtml nextaw is drop in replacement of libXaw. So all packages which depend on libxaw can be used with nextaw.
According to pkgstats not many people do so (0.13 %). Cite: "Just replace libXaw.* or libXaw3d.* with libneXtaw.so.?.? and make all symlinks that were pointing to libXaw point to libneXtaw " That means to me, the user has to manually set symlinks, an if he is able to understand this and to do so, he should also be able to compile from a PKGBUILD in AUR. Regards Stefan
On 12 June 2010 23:40, Stefan Husmann <stefan-husmann@t-online.de> wrote:
Am 12.06.2010 19:06, schrieb Sergej Pupykin:
On 06/12/2010 07:54 PM, Stefan Husmann wrote:
this is a proposal to remove nextaw from community. It is not needed by any community package. It once was a dependency of siag-office, which has been moved to unsupported long ago and is still unmaintained there.
I am not against removing, but as I understand http://siag.nu/neXtaw/usage.shtml nextaw is drop in replacement of libXaw. So all packages which depend on libxaw can be used with nextaw.
According to pkgstats not many people do so (0.13 %).
Cite: "Just replace libXaw.* or libXaw3d.* with libneXtaw.so.?.? and make all symlinks that were pointing to libXaw point to libneXtaw "
That means to me, the user has to manually set symlinks, an if he is able to understand this and to do so, he should also be able to compile from a PKGBUILD in AUR.
Taking the replacement into consideration, judging from pkgstats, I vote for removal. -- GPG/PGP ID: B42DDCAD
Am 12.06.2010 23:04, schrieb Ray Rashif:
On 12 June 2010 23:40, Stefan Husmann<stefan-husmann@t-online.de> wrote:
Am 12.06.2010 19:06, schrieb Sergej Pupykin:
On 06/12/2010 07:54 PM, Stefan Husmann wrote:
this is a proposal to remove nextaw from community. It is not needed by any community package. It once was a dependency of siag-office, which has been moved to unsupported long ago and is still unmaintained there.
I am not against removing, but as I understand http://siag.nu/neXtaw/usage.shtml nextaw is drop in replacement of libXaw. So all packages which depend on libxaw can be used with nextaw.
According to pkgstats not many people do so (0.13 %).
Cite: "Just replace libXaw.* or libXaw3d.* with libneXtaw.so.?.? and make all symlinks that were pointing to libXaw point to libneXtaw "
That means to me, the user has to manually set symlinks, an if he is able to understand this and to do so, he should also be able to compile from a PKGBUILD in AUR.
Taking the replacement into consideration, judging from pkgstats, I vote for removal.
-- GPG/PGP ID: B42DDCAD
Okay, done.
participants (4)
-
Ionuț Bîru
-
Ray Rashif
-
Sergej Pupykin
-
Stefan Husmann