On Sun, Nov 23, 2014 at 10:52:54PM +0500, Andrey Rahmatullin wrote: > On Tue, Nov 18, 2014 at 09:24:15PM +0900, Charles Plessy wrote: > > > 2.2.1 says "the packages in main > > > > > > must not require or recommend a package outside of main for > > > compilation or > > > execution (thus, the package must not declare a "Pre-Depends", "Depends", > > > "Recommends", "Build-Depends", or "Build-Depends-Indep" relationship on a > > > non- > > > main package)," > > > > > > In practice there is a consensus that this also means "packages must not > > > access > > > external network servers" which conforms to the spirit but not to the > > > letter of > > > this section. > > > > > > Note that there may be other requirements which are not codified, as > > > mentioning > > > only things that are packaged is not enough, it should say something like > > > "must > > > not use any stuff except for packages in main". > > > > Hi Andrew, > > > > I guess that it is implicit from the defintion of contrib that follows in > > 2.2.2: > > > > The contrib archive area contains supplemental packages intended to work > > with > > the Debian distribution, but which require software outside of the > > distribution > > to either build or function. > I've just understood both these statements mention requiring something > non-free to *function*. > Do we allow packages in main to require external services to function?
There are far too many special case (think: whois, DNS, youtube-dl) to write something meaningful I am afraid. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141123185608.GB16143@yellowpig
