> On Mon, Jan 21, 2008 at 19:08:43 -0500, Norman Ramsey wrote: > > > Package: autoconf > > Version: 2.61-4 > > Severity: serious > > Justification: Policy 3.5 > > > > Policy 3.5 says: > > > > Every package must specify the dependency information > > about other packages that are required for the first to work > > correctly. > > > > autoconf merely 'recommends' automake, which is not a sufficiently > > strong dependency, as shown by what bit me today: > > > autoconf works just fine without automake. > The autoreconf command doesn't, but its functionality isn't necessary > for autoconf.
Yes, but autoreconf is part of the autoconf package. You are therefore shipping a package which includes a command that doesn't work. I can't believe this is what the authors of the Debian Policy intended. If you really want to draw this distinction, package autoreconf separately (with suitable dependencies). If on the other hand you insist on bundling the two programs, so that the only way to get autoreconf is to install the autconf package, then the dependency on automake is real and should be part of the debian/control file. Or is there something obvious I'm missing here? Norman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
