What's best way to manage cups configuration? (Re: [Pkg-cups-devel] Bug#343566: cupsys: /etc/cups/cups.d/ports.conf contains errornous string after upgrade.)

[Martin Pitt]

Hi!

Kenshi Muto [2005-12-17 15:14 +0900]:
> In this thread, I'd like to ask you what's best way to manage CUPS
> configuration roused by Christopher.
> 
> > BTW, was it really necessary to split out these settings from cupsd.conf? 
> > This affects 3rd-party printer configuration tools like kprinter, and 
> > others, I imagine, since now they spit out errors about strange "include" 
> > elements in cupsd.conf, and can't control the Ports, etc. settings as they 
> > used to. In short, these changes are a real pain. It would be nice if you 
> > could change the debconf system around to keep asking the new questions, 
> > but NOT to split anything out of cupsd.conf.
> 
> The reason why I splited Ports/Listen and Browsing from cupsd.conf is
> to free us from parsing complex big configuration and to make
> managing by debconf more easier.

Right, that's the way it should be.

> But as Christopher said, this change may break other configuration
> tools.
> 
> - Should we back splited configuration to one big file?

No, it is a pain, because cupsd.conf is a big conffile that gets
changed in cups from time to time. No need to bother users with dpkg
questions if they only changed Ports/Listen parameters.

Packages should not modify conffiles of other packages, i. e. kprint
modify /etc/cups/cupsd.conf. They may, however, change other package's
configuration files, so splitting out these settings into separate
files actually helps these packages.

Thanks,

Martin

-- 
Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org

In a world without walls and fences, who needs Windows and Gates?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cups-devel/attachments/20051220/fa0c956c/attachment.pgp