Re: What I should do for official ruby backport?

[Johann D. <joh...@it...>]

Aivils Stoss wrote:
> Hi, folks
> 
> Motivation:
> 1. James Simons will not keep clear code in ruby CVS.
> 2. Nobody use Linux in my home , if can't start triple Freeciv,
> Quake3Arena, and so on.
> 
>      Sametimes I can find small bugs in one-two month time period. It's
> good enough
> for me, but my be abnormality in public area.
> 
>      Johan alwways made backport. So next time I wait for it, then release
> my
> package.
> 

I indeed backport the force-feedback related drivers to 2.4. The reason 
for this are:
1. I use 2.4 (2.5+ide used to be a bad combination)
2. Users are mainly gamers. Gamers use NVidia cards. NVidida drivers are 
for 2.4. -> users probably want 2.4.

Now, this is not a complete backport of ruby at all. It only included 
small pieces of the input layer, plus the iforce and hid drivers.

I was planning to wait until Brad's patches would be included into 
2.4.20-preX to send iforce to Alan Cox (and later hid).

> I will heard veteran hints. I hope You don't recommend stop it.

I am not sure what your patch exactly does. But if it's a full ruby 
back-port, I am not sure it is really worth the pain (IMHO). As far as I 
know, ruby is not going to make it into 2.4. It must be quite hard and 
time-comsuming to track the console+input thing, isn't it ?
Are there many users out there *needing* ruby in 2.4 ? If it's only for 
testing purposes, I guess they can use 2.5.

-- 
Johann Deneux