Santiago Vila wrote: > > I think this is an absolutely dreadful idea. > > > > Technical decisions should be made by the relevant experts, according > > to their own views, and matching the code that they have written or > > plan to write. > > > > So, in this example, the menu policy should remain with the menu > > package. > > In such case, the debian-policy package should at least contain a clear > and comprehensive list of all the other sub-policies that should be taken > in account when writing a Debian package. > > Frankly, I would much prefer to read them all by installing a single > package.
I think we should move the menu hierarchy out of the menu documentation and into policy. It is something that could benefit from being maintained by the policy list, and it needs the weight of policy behind it to ensure that all packages be made to comply with it, so that the menu hierarchy is kept consistent. The remainder of the menu documentation has nothing to do with policy, it describes how to run update-menus, the format of a menu file, and so on. A package that does not do that correctly will be obviously buggy, and so there's no reason to make it policy to enforce it. (See my earlier long posting to debian-devel for a clearer description of why I feel this way. http://www.debian.org/Lists-Archives/debian-policy-9901/msg00067.html) -- see shy jo
