Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 121288 - synaptics driver does install to wrong path for xorg modular
Summary: synaptics driver does install to wrong path for xorg modular
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-02 04:51 UTC by Björn Ruberg
Modified: 2006-02-02 06:09 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Ruberg 2006-02-02 04:51:32 UTC
When merging synaptics (X11 driver for some nice touchpad features) it install synaptics_drv.so to /usr/lib/modules/input/ instead of /usr/lib/xorg/modules/input so that Xorg-7 does not find it.
After copying it to the right directory Xorg finds it and it works.

Probably a dev can solve this very fast but I may try to fix the ebuild on my own if someone wants me to.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-02-02 05:38:45 UTC
Looks just fine with synaptics-0.14.4-r2

<snip>
                if has_version ">=x11-base/xorg-x11-7.0" || has_version ">=x11-base/xorg-server-0.99"
                then
                        exeinto /usr/$(get_libdir)/xorg/modules/input
                        doexe synaptics_drv.so
                else
                        exeinto /usr/$(get_libdir)/modules/input
                        doexe synaptics_drv.so
                fi
</snip>
Comment 2 Björn Ruberg 2006-02-02 05:44:45 UTC
Indeed, that should work.
With the stable version of synaptics (0.14.2) it does not.
Maybe the "migrating to X.org-7" guide should be updated to use ~arch x11-drivers/synaptics too.
Comment 3 Joshua Baergen (RETIRED) gentoo-dev 2006-02-02 06:09:48 UTC
The general idea is that mixing ~ and stable packages is bad, and throwing masked packages into that mix is even worse.

When things move from testing to stable we try to check for things like this, but when things are in testing they're only supposed to work against testing packages.