On Tue, Mar 22, 2005 at 01:18:41PM -0500, Marc Sherman wrote: > Colm MacCarthaigh wrote: > >On this front, I've been thinking it would be better to use > >apt-listchanges --profile option, ie use --profile=apticron and allow > >end-users to pick the output they desire that way. with defaults > >somewhat like: > > > > [apticron] > > which=both > > headers=1 > > > >I presume such a solution would be acceptable? > > Yeah, I was thinking the same thing. > > My worry there is that listchanges.conf is owned by another package, > though it doesn't appear to be a conffile. Does that mean that you're > allowed to write to it in your maintainer scripts? I'm not sure.
I've been researching the policy on the same thing, I've found some packages that do it - nagios for example does it with httpd.conf. > Really, listchanges.conf should be listchanges.d, which each [foo] > section becoming a file listchanges.d/foo. Depending on what I find in policy, I think I might feature-request just that myself. -- Colm MacCárthaigh / HEAnet, Teach Brooklawn, / Innealtóir Líonra +353 1 6609040 / Bóthar Shelbourne, BÁC, IE / http://www.hea.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
