Bug#646166: § 2.2.1: clarify why "must not require" includes Recommends

2011-12-25 Thread Russ Allbery
David Paleino writes: > section § 2.2.1 of the Policy reads as follows: > [..] the packages in main: > - must not require a package outside of main for compilation or execution >(thus, the package must not declare a "Depends", "Recommends", or >"Build-Depends" relationship

Bug#646166: § 2.2.1: clarify why "must not require" includes Recommends

2011-10-21 Thread Charles Plessy
Le Fri, Oct 21, 2011 at 09:45:10PM +0200, David Paleino a écrit : > > Automatic installation of Recommends is a per-system configuration option, and > shouldn't be assumed in Policy IMHO. > > I suggest to drop "Recommends" from that sentence or, if we want to make sure > no non-main packages get

Bug#646166: § 2.2.1: clarify why "must not require" includes Recommends

2011-10-21 Thread David Paleino
Package: debian-policy Severity: wishlist Version: 3.9.2.0 Hello, section § 2.2.1 of the Policy reads as follows: [..] the packages in main: - must not require a package outside of main for compilation or execution (thus, the package must not declare a "Depends", "Recommends", or