On Sun, Nov 20, 2005 at 09:26:37PM +0100, Nicolas Boullis wrote: > On Sun, Nov 20, 2005 at 12:13:48PM +0100, Bill Allombert wrote: > > Hello Debian developers, > > > > When doing research about circular-deps, I looked at a lot of packages > > that are split between a binary package and a data package. This is a > > good thing since this reduce the total siez of the archive, however > > there are simple rules that should be followed: > > > > 3) Keep the files that 'signal' executables in the same package than the > > executable (e.g. menu file, program manpage). > > Why? I agree that it menu files and manpages are generally not that > large, but what would it break to have them in pkg-data? > (I would consider it strange to have such files out of the main pkg > package, but it looks policy-compliant as far as I can see...)
Because if you install the pkg-data but not pkg, the manpage will be available but not the program which is not nice. For menu it is not a problem provide you write the menu entry correctly ?package(foo):... and not ?package(foo-data). This way update-menus check whether foo is installed before using the entry. Anyway I did not claim this was mandated by policy. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
