LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-12-2016, 07:20 PM   #1
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,712

Rep: Reputation: 558Reputation: 558Reputation: 558Reputation: 558Reputation: 558Reputation: 558
why slackware no have xf86-input-libinput ?


Simply , why?

In to a first look , aparently is a nice packet.

https://freedesktop.org/wiki/Software/libinput/



X.Org libinput driver

The X.Org libinput driver is a thin wrapper around libinput and allows for libinput to be used for input devices in X. This driver can be used as as drop-in replacement for evdev and synaptics. Simply build and install in your $PREFIX, then install the config file in /etc/X11/xorg.conf.d/. Restart X and the libinput driver will take over your devices.

Last edited by USUARIONUEVO; 03-12-2016 at 07:22 PM.
 
Old 03-12-2016, 07:46 PM   #2
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,669

Rep: Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220
A post from one of your favourite threads
 
Old 03-12-2016, 08:08 PM   #3
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,712

Original Poster
Rep: Reputation: 558Reputation: 558Reputation: 558Reputation: 558Reputation: 558Reputation: 558
rworkman says works well on fedora, but nothing more.

i ask , because i dont know if is for "Incompatibility" , or other reason.
 
Old 03-12-2016, 08:10 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2 and Slackware64 -current (AKA Slackware64 15)
Posts: 3,787

Rep: Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139Reputation: 2139
Quote:
[...]we'll let Fedora do the testing on libinput support and work out the kinks.
So, I think it's "not enough testing yet".
 
Old 03-12-2016, 08:55 PM   #5
Gerard Lally
Senior Member
 
Registered: Sep 2009
Location: Brú na Bóinne, IE
Distribution: Slackware, NetBSD
Posts: 1,924

Rep: Reputation: 1398Reputation: 1398Reputation: 1398Reputation: 1398Reputation: 1398Reputation: 1398Reputation: 1398Reputation: 1398Reputation: 1398Reputation: 1398
Quote:
Originally Posted by USUARIONUEVO View Post
rworkman says works well on fedora, but nothing more.
Nothing more? Really?

These threads are ridiculous. I'd like to have dar, zpaq, postgresql, fcron, mksh, rxvt-unicode, racket and the forked heirloom-doctools included by default. Other people have their own lists. Where exactly do you want to stop?

Last edited by Gerard Lally; 03-12-2016 at 09:09 PM.
 
Old 03-12-2016, 09:08 PM   #6
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,712

Original Poster
Rep: Reputation: 558Reputation: 558Reputation: 558Reputation: 558Reputation: 558Reputation: 558
Hey , i say nothing more , around the libimput, i know rworkman works in slackware packages and slackbuilds a lot.

All my respect ,is a developer.

Im not need libimput , xf86-input-libimput , im not want, is only curiosity , because i read that package support touchscreens and other imput hardware , and im not sure why are not in slackware,only that.

@gezley
Ridiculous are people putting only trash , when users ask something, is a question , only a question , understand this?


that replaces 2 packages on xorg , but probably , the separate packages have more "hardware support" , or something...or not, i dont know, and i ask.

Richard Cranium , point to not big testing, then better go to work packages , and wait...probably is that.


I hope all can sleep this night after read this ridiculous thread. :=)

Last edited by USUARIONUEVO; 03-12-2016 at 09:15 PM.
 
Old 03-12-2016, 09:11 PM   #7
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,323

Rep: Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523
When it's considered ready and needed by Slackware packages it will be included by Pat.

So far, synaptic works fine
 
Old 03-12-2016, 09:16 PM   #8
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,669

Rep: Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220Reputation: 2220
Quote:
In to a first look , aparently is a nice packet.
And rworkman agrees that "libinput seemed to be a completely seamless transition for two machines here in front of me".
But Slackware-current is meant to be leading edge, not bleeding edge. A change in drivers for commonly used input devices is not to be undertaken lightly.
 
1 members found this post helpful.
Old 03-12-2016, 09:16 PM   #9
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 1,712

Original Poster
Rep: Reputation: 558Reputation: 558Reputation: 558Reputation: 558Reputation: 558Reputation: 558
Quote:
Originally Posted by willysr View Post
When it's considered ready and needed by Slackware packages it will be included by Pat.

So far, synaptic works fine
then you point the same , need more testing to go with that.

OK , thanks.
 
Old 03-13-2016, 08:06 AM   #10
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,460
Blog Entries: 15

Rep: Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040Reputation: 2040
xf86-input-libinput is not part of mainstream Xorg's drivers yet. Libevdev and Libinput both have similar working stacks, but libinput was written for Wayland to give input support. Because Wayland isn't part of Slackware yet, libinput and xf86-input-libinput are not needed, and xf86-input-evdev and libevdev still work fine with X and programs that use it.

I'm certain that when Wayland is added, Patrick will probably consider xf86-input-libinput for inclusion, and if not, pass it off for the community if needed via SBo. Until then, you are free to craft and submit packages for it to SBo.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
xf86-input-vmmouse-13.1.0 uses wrong udev rules directory chrisVV Slackware 1 01-17-2016 03:41 AM
xf86-input-synaptics tm2383 SUSE / openSUSE 1 05-07-2015 05:38 AM
xf86-input-synaptics-1.4.0 causing sluggish cursor movement uhgreen Linux - Laptop and Netbook 1 05-01-2011 05:52 PM
xf86-input-keyboard and xf86-input-mouse masked CollieJim Gentoo 4 11-09-2009 09:57 PM
Howto write XF86 Input Module? ZX_SA Programming 0 05-11-2005 09:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:51 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration