Sune Vuorela <[email protected]> writes: > To be honest, I also have a hard time seeing the issues, but after > participating two days in a row debating this with different people in > #debian-devel, I just thought that something must be unclear. I asked a bit, > and a specific "should" the primary blame. > >> If it is desirable for two or more related packages to share a >> configuration file and for all of the related packages to be able to >> modify that configuration file, then the following should be done: > That should over there -------------------------------> ^^^^
Right, this isn't currently mandatory. However, one is generally expected to have a pretty good reason for violating a Policy should, not just "I didn't feel like doing the work." I could see hacking together something in the interim while work was being done on the program to update the shared configuration file, but it seems like some forward progress on that would be in order. It sounds like a bit too much expediency is happening at the cost of doing things the right way in the long run. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
