On Sat, Jul 17, 2010 at 11:34:26AM -0400, Holger Levsen wrote:
On Samstag, 17. Juli 2010, Jonas Smedegaard wrote:On Sat, Jul 17, 2010 at 03:59:49PM +0200, Jonas Smedegaard wrote:>Sorry, I do not have an easy solution, only a touch one: For each >and every package, the Debian maintainer *must* be convinced to >officially support whatever configuration customization Debian Edu >needs to apply.no, they only need to provide a way to allow customisation of configuration files, eg via /etc/$package/conf.d/
What "no"?Yes, conf.d mechanism is one of several ways a package maintainer can choose to support configuration customization.
My point is that if package configuration is derived using a mechanism not supported by the package maintainer - no matter if supported upstream or if the mechanism happens to fit Debian Policy - then Debian Edu has a higher risk of failing to support major system upgrades.
- Jonas -- * 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