SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Wed May 24 04:51:46 UTC 2017
...
l/newt-0.52.20-i586-1.txz: Upgraded.
But still no bidi
Well, I'll provide it in the Slint repos with it then, no worries.
The patch was reverted because it broke things. But also that was a long time ago and I don't see references of tries to get it in again afterwards. I really think a feature like that should not just be applied at distro level. If you want it I would really suggest bringing it up again with upstream.
The patch was reverted because it broke things. But also that was a long time ago and I don't see references of tries to get it in again afterwards. I really think a feature like that should not just be applied at distro level. If you want it I would really suggest bringing it up again with upstream.
CHANGES says:
Code:
0.52.1
- revert bidi patch, objections by Jeremy Katz about
anaconda breaking
I don't think we should really worry about Anaconda breaking in Slackware, even considering that Slackware alumni contributed to this project
I will feed Fedora's bug tracker but I think that Miroslav Lichvar is already aware of the issues reported in the Debian bug tracker (although some have needed a lot of time to be addressed)[1] and there is no incentive for Fedora in bringing bidi to newt, so I won't hold my breath waiting for a positive answer.
On the other hand newt with the bidi patch have been used for years in the Debian installer through whiptail, with no reported issue.
As I have already written Fedora is still considered upstream but only for historical reasons, as far as I know.
[1]I have brought this issue to Alastair McKinstry on 06/11/2015 and he answered
Code:
I think maintaining a separate branch, with '--enable-bidi' sounds like
the right approach.
(holding work in git makes this straightforward, and fedora can merge as
desired).
Last edited by Didier Spaier; 05-24-2017 at 05:27 AM.
0.52.1
- revert bidi patch, objections by Jeremy Katz about
anaconda breaking
I don't think we should really worry about Anaconda breaking in Slackware, even considering that Slackware alumni contributed to this project
Well, it's a library. An application using that library broke because of a change. I would find it risky to reduce it to "oh but it's just anaconda..."
Quote:
Originally Posted by Didier Spaier
I will feed Fedora's bug tracker but I think that Miroslav Lichvar is already aware of the issues reported in the Debian bug tracker (although some have needed a lot of time to be addressed)[1] and there is no incentive for Fedora in bringing bidi to newt, so I won't hold my breath waiting for a positive answer.
The way I see it there's 2 options. If it's worth having the feature, then there should be some effort to get it upstream. If upstream won't have it, there is most likely a legitimate reason why. While finding a reason for including it is fairly easy, I'm less clear about the counter argument. So at the very least that needs to be cleared up.
Well, it's a library. An application using that library broke because of a change. I would find it risky to reduce it to "oh but it's just anaconda..."
AFAIK the only package that depends on newt in Slackware is NetworkManager (for the TUI client). I will check if it's broken applying the bidi patch.
Quote:
The way I see it there's 2 options. If it's worth having the feature, then there should be some effort to get it upstream. If upstream won't have it, there is most likely a legitimate reason why. While finding a reason for including it is fairly easy, I'm less clear about the counter argument. So at the very least that needs to be cleared up.
Wed May 24 04:51:46 UTC 2017
...
l/newt-0.52.20-i586-1.txz: Upgraded.
But still no bidi
Well, I'll provide it in the Slint repos with it then, no worries.
I downloaded and looked at that patch, but when was it ever the policy here to do feature addition patches? Especially when it's a) a large non-trivial patch b) peppered with comments about how things aren't working yet c) upstream tried to take it but ended up reverting it when it broke things.
I'll be happy to have that functionality if the proper channels ever accept it, but sorry -- I really don't think accepting it here is a good idea.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
