On Thu, 2005-11-17 at 21:22 -0500, Francois Marier wrote: > On Thu, Nov 17, 2005 at 06:05:46PM -0800, Ross Boylan wrote: > > On the other hand, since some people (e.g., me) might not care about > > doing DAO, maybe leaving it as recommends would be best. This seems > > delicate: I think normally packages don't depend on things they can live > > without--to avoid bloat. But k3b clearly targets the novice, and they > > may just find it confusing if some of the pieces are missing. In fact, > > I guess I did too :) > > I would personnally favor ease of use over the increased dependency. I think in this case novice ease of use = increased dependency. That is, if the user installs the package, and then finds it doesn't work (or even just that there are warning messages) because some packages are missing they may be confused (e.g., I thought the warnings were fatal). If the appropriate packages (cdrdao) are dependencies, they will be installed automatically.
This is probably not a good enough reason to make packages that aren't essential a dependency. > > > Does that raise any policy issues for Debian? Aside from the general > > issue of manipulating installed programs behind the back of the package > > management system, I assume that setting programs to run as root entails > > security risks. > > Well, it's not done by the package installation but rather by an external > configuration program so it's probably not breaking policy, but you have a > good point, it could probably be integrated better into Debian. I'll have > to think about this one though. > > > Thanks for all the info. I do think putting some of this in > > README.Debian would be good. > > I thought about suggesting running k3b as root, but the cdrecord message > already takes care of this. Did you have anything else in mind? Since cdrecord was running inside of k3b, the messages it emitted weren't enough to suggest to me that k3b should be run as root. For the benefit of others equally dense, I think it would be worth suggesting running k3b as root in the README.Debian, along with the advantages and any possible risks (e.g., security, or the fact that ordinary users may not have access to root) of doing so. Some discussion of the setup message about changing file permissions would be good too. E.g., is this recommended or not? I also suggest adding something like "k3b may complain if cdrdao is missing. If you are recording audio CD's you need cdrdao; otherwise you can ignore the warning." I don't know if that's completely accurate. I also don't know what similar issues may arise with DVD's. > > > One awkwardness was that after I went through the setup I had to exit > > the program and restart to get it to recognize the output devices. > > Should I file a bug with Debian or upstream, send them a note upstream, > > assume it's fixed in later versions .....? > > Well, it would be better to file this bug on the upstream bug tracker > (http://bugs.kde.org, under the "k3b" project) since it doesn't relate to > the Debian packaging. However given the fact that there are hundreds of > bugs on that bug tracker, I believe that the upstream developer will only > have a look at it if it has been reproduced sucessfully on the latest > version of k3b (0.12.7, the one in unstable). Doing nothing sounds like the best option! Thanks for saving me the trouble. > > Francois -- Ross Boylan wk: (415) 514-8146 185 Berry St #5700 [EMAIL PROTECTED] Dept of Epidemiology and Biostatistics fax: (415) 514-8150 University of California, San Francisco San Francisco, CA 94107-1739 hm: (415) 550-1062 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
