Hello Arne! On 27/01/2012 18:26, Yaroslav Halchenko wrote: > Hi Arne -- thanks a lot for following up! > So Nicolas -- ready to take the blame? ;)
If it is ok for all of you, I am fine with taking the blame! :-) On 27/01/2012 17:32, Yaroslav Halchenko wrote: > I guess you do have a > beast (kinect) to enjoy, right? ;) To answer you question Yaroslav, we bought a kinect few month ago in the lab to test few things and it was on my office mate's desk since then. I was curious about it and started to see how this beast could perform... On 27/01/2012 17:35, Yaroslav Halchenko wrote: > or may be just bluntly under NeuroDebian Team, since you are pretty much > a part of it now ;-) ) > > On Fri, 27 Jan 2012, Yaroslav Halchenko wrote: >> > we might alternatively start libfreenect-maint team on alioth which >> > would be listed as the maintainer while we all stay in uploaders... what >> > you think? If everybody in the neurodebian project, we can stay in it, that what you prefer. I am not sure, it is wise to open a project on its own for one package but I might be wrong. What do you prefer. (off topic question: there is a neurodebian project on Alioth, and pkg-exppsy which has more people... which one should be used?) On 27/01/2012 18:25, Arne Bernin wrote: >> - solution 1: installing libfreenect0.1 package installs a modprobe rule >> > which blacklist the module gspca_kinect. But it makes the v4l2 interface >> > unavailable which is bad for those who want to use it. > What about asking the user via debconf what he wants and make the > blacklisting as an option? Seems the easiest solution for me... Actually, I had forgot this possibility... It is actually better than the statu quo but it still remains the question of the default action. What surprises me the most is that issue of userspace driver and kernel space driver seems not to have been raised earlier with other devices... Cheers, Nicolas
signature.asc
Description: OpenPGP digital signature
