[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Local, custom and persistent (/etc) config files in Debian

Hi Héctor,

On Fri, Oct 01, 2010 at 04:27:42PM +0100, Hector Oron wrote:

I would like to do some changes to some configuration files (under /etc)... done
-->  I create a package-config which changes all my configs

I would like to modify previous configuration files (filtered by sed)
and be able to change unchanged files as well... done
-->  I create a package-config even more hackish

Which are current practices people doing in such cases? Is there a
better flow to customize configuration files via package system?

Are practices described on debathena [1] or config::model [2]
something we should follow?

[1] http://debathena.mit.edu/config-packages/
[2] http://wiki.debian.org/PackageConfigUpgrade

I feel your question is inappropriate for this list, which is for non-technical discussions. I suggest to repost to either d-devel or d-user, depending on what you mean by "we" in last sentence above:

"We" (Debian developers) must obey Debian Policy for all packages, which means we are quite limited in how we can have one package configure another. "We" (subdistributions, sysadmins and other Debian users) on the other hand can do whatever we like - but can only expect non-interactive upgrades of pieces not customized by us.

Quite interesting dilemma, but wrong list IMO.

- Jonas

P.S. Feel free to cc me if posting to d-devel about the develper part of this, as I am quite interested in this particular issue, but am not currently subscribed to that list.

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

Reply to: