On Sunday 03 September 2006 11:08, you wrote: > Hi Slaven, > > I apologize for taking so long to answer you. > > I've been thinking about this bug for a while and I think you're right in > saying that K3b should work out of the box. > > So what I am thinkin of doing is removing k3bsetup from the Debian package > and replacing the cdrecord warning with a "do a dpkg-reconfigure cdrecord > and set it as SUID if you are having problems" message (some people report > success with a non-SUID cdrecord). Afterall, that's the proper fix on > Debian. > > I feel like k3bsetup makes perfect sense in the upstream package since K3b > is designed to work on all systems and this tool helps solve that problem. > However, on a specific distro, it shouldn't be necessary and should be > replaced by a more specialized mechanism. > > What are your thoughts on that? > > Francois
Hi Fracois, I actually wanted to suggest the same solution, but I was afraid it was too radical. I think having k3bsetup change permissions disregarding debconf may be potentially dangerous. So, yes, I'm all for removing k3bsetup, especially because it's already nonfunctional in etch. Besides, it is much better to have one systemwide configuration tool -- namely debconf -- than to do system administration with a bunch of different tools whose functions may overlap here and there. There are a few things that come to my mind should you go ahead and remove k3bsetup: What if somebody turns off debconf for configuring packages? In that case dpkg-reconfigure wouldn't work, I guess. Perhaps we can assume that if someone turns off debconf, one is smart enough to change permissions by hand? Wording of new messages has to be very careful, so that novice sysadmin can understand it well. My experience so far is that most of sysadmins read only the first sentence of a warning message and then proceed doing whatever first comes to their mind. What about cdrdao? It does not allow for setting suid through debconf. Perhaps I should submit a whishlist bug against cdrdao? There may be quite a few people who like k3bsetup, and who will want it back. Ready yourself for some hate email ;-). There are some other warning messages that k3b gives which are misleading. For example k3b diagnostics suggests installing package cdrtools, but there is no such binary package in debian. That may lead people to download and install cdrtools from upstream sources... I know it sounds silly, but it happens a lot, and it usually ends up with a broken system. Should I submit separate bug reports for these? Well, thanks a lot for your attention to this problem and for your work in maintaining k3b and other packages. Let me know if I can help with anything. Cheers, Slaven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
