The differenced introduced from w3m-0.3-r1.ebuild to w3m-0.3-r2.ebuild was that the mouse support is disabled when the gpm USE variable is not defined. This is completely _unnecessary_, since even without gpm, there _is_ mouse support in xterm and alike and doing this disable it. Please revert the changes, or (to keep the flexibility given by option 6) change the line use gpm &>/dev/null && echo y || echo n to echo y
The ability to turn off mouse support is there for people that have issue's with gpm on there machines with w3m, sometimes gpm will corrupt w3m and make it unuseable. If you want mouse support just add gpm into the your use. If you want we maybe just be able to change the use to something like "mouse" but I'm not sure thats a special request that needs to be passed up to the leads, since USE variables are not arbitrarily added. Maybe it's there is something similar thats already there I will look into it. Naz
What does mouse support in w3m has to do with gpm!!!?? I don't have gpm, and still I have support for mouse on w3m! If gpm is the problem, then those people shouldn't have it in the first place. What's the point in having a program that only causes problems after all? I can't be more clear on that: one doesn't need gpm for controlling w3m with mouse. So WHY isn't mouse support enabled when there is NO gpm!?
Ok well I will revert to the older style ebuild .. but if it causes any issue's with gpm on some peoples machines I will go back to the current ebuild. In the mean time I'm going to keep this bug open so I can maybe looking at patching out the code that causes gpm support to compile so we can still build the rest of the mouse support just minus gpm support Naz
done.. naz
