Joey Hess wrote: > Manoj Srivastava wrote: > > You misunderstand me. I never intended to subsume menu.sgml > > into policy.sgml, you have correctly come up with some reasons why > > that would be silly. > > > > Have I satisfied your objections? > > Yes.
Unfortunately, I've come up with one more. :-/ menu.sgml is the only documentation there is for the menu package. If menu.sgml is moved into the policy package, menu will not have any useful docs in /usr/doc/menu. menu could be changed to depend on debian-policy and have a symlink, but that will require a lot of people who don't care about debian policy to install the package (and 350k isn't anything to sneeze at (and it'll get bigger as more subpolicies are moved into it)). Menu could just suggest debian-policy and have a README that points to it, but this will mean even more work for someone who just wants to read the user-level documentation for menu. I would say split the user-level and developer-level documentation of menu, keep the user-level in the menu package and move the developer-level into the debian-policy package; but there's a lot of overlap - users may need to know the format of menu files, the menu hierarchy, even the format of menu-methods files. If it can't be split, I'd rather the developers had to do a little extra work to get the menu docs, instead of the users having to do extra work. But I agree with you on general principals, this is just a technical problem. Can you think of any good solution? -- see shy jo
