On Fri, Dec 12, 2008 at 03:08:03PM +0100, Artur Grabowski wrote: > Marc Balmer <m...@msys.ch> writes: > > > Your are wrong. When you install CUPS, a message is displayed. > > That message can be redisplayed at any time using 'pkg_info -M cups'. > > Is this like Postfix where postfix is disabled by pkg_add -u and the > message about enabling it drowns in the bazillion of lines about > rebuilding icons or whatever that spam is about? > > Sorry. but a few lines with "Hi, we just disabled your production > critical service. you have to enable it again" hidden in spam about > rebuilding some xml crap, icon databases and whatever is not good. > > I think postfix was fixed to not break this way (at least it didn't > shut down when I upgraded a few hours ago), if this is the issue with > cups, it should be fixed too.
actually, it's upgrading base that is likely to break cups, assuming you rely on cups-enable and not come up with your own solution. cups-enable is not run automatically when the package is added. we don't want to overwrite system binaries by default, right? keep in mind this discussion started with someone not being able to find the script that would put them in such a situation. cups-enable is there as a convenience. there are other ways to deal with cups. but those require some thought on the part of the sysadmin. I posted the link to the original discussion about this script for a reason. you have a point about too much noise when installing/upgrading, but it has been improved at least a little. all the "important" message are displayed at the end and not mixed in with the icon/xml update "spam". one last note: pretty much every driver that can be used with cups can be used with base lpd, it's just a little more work ... imo the best solution is to implement ipp in lpd and tell cups to screw off since it would really not be offering more than the convenience/ headache dichotomy we are discussing, but that is just me. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
