Re: Source section (debian/control)
Jeroen van Wolffelaar <email@example.com> writes:
> On Sat, Apr 30, 2005 at 08:40:41PM +0200, Daniel Leidert wrote:
>> I have a question: In which case, a package can go into main or must go
>> into contrib/non-free is described in the Debian policy. But when do I
>> need to put the source into contrib/non-free? The situation: I have a
>> GPL licensed, python based application, which needs python2.3-profiler
>> (non-free), so the binary package can't go into main. Therefor i will
>> put it into contrib. Do I have to assign the source as 'contrib' too?
> Technically, it doesn't matter. Whatever you use in debian/control is
> not copied to .dsc (it doesn't have section & priority header), it's
> just used as default for the binary packages in the next stanza's of
> Sources do have a priority and section, but at the moment, that's
> exclusively set by ftp-master. It seems to me it'd be nicer to have
> those fields in the .dsc indeed and then also checked by the ftp-master
> scripts, but that's definitely a post-sarge issue.
How does ftp-master decide?
When does a source that builds contrib packages go to main? When it
also builds main packages?