<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282967>
I can confirm that Kino's Preferences/IEEE 1394/dv1394 Device entry widget is *only* for dv1394 and not raw1394 by design because, of course, libraw1394 has /dev/raw1394 hardcoded. I think it is very reasonable to offer an environment variable to override this hardcoded default. Thank you for the suggestion. Just for giggles, I am going to show you a short-sighted response I had prepared before reading Daniel's suggestion. Remember, I no longer feel this way, and I just include it for our enjoyment :-) ... I do not believe in offering this flexibility because it creates support headaches. Believe it or not, most users--even our geeky Linux brethren--have great difficulty understanding that something does not work because what is in an app's configuration does not match the filesystem. Quite often, to respond to a problem report, I have to make just a couple of exchanges to ensure a proper configuration. I have been supporting Linux 1394 for almost 6 years, and this is the first request I can recall for this change. So, do you think I am going to make an interface change to a heavily dependent library for one requester and add to mine and others' support headaches? Hell fucking no! And if I keep the interface by simply adding a new variant of raw1394_new_handle(), do you think I am going to change Kino to require a new version of libraw1394 that no distro has and to offer a way for users to configure thereby increasing their likelihood of breaking it? No. The only reason I have to do this for dv1394 today is because of a design fault of dv1394 and the lack of consistency in device file naming. If you are advanced enough to not use /dev/raw1394, then you are advanced enough to make the status quo work on your particular system. And I see you have, by using a simple symlink. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
