Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes:
> On Sat, Apr 30, 2005 at 08:40:41PM +0200, Daniel Leidert wrote:
>> Hello,
>>
>> 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
On Sat, 30 Apr 2005, Daniel Leidert wrote:
> Only that I really understand it: Following your answer, let's say there
> is an application which provides some extra functionality, but these
> extra-functions need a package outside main to compile. The core
> functionality does not need a package out
Am Samstag, den 30.04.2005, 15:56 -0300 schrieb Henrique de Moraes
Holschuh:
> On Sat, 30 Apr 2005, Daniel Leidert wrote:
> > 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 binar
On Sat, Apr 30, 2005 at 08:40:41PM +0200, Daniel Leidert wrote:
> Hello,
>
> 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
> GP
On Sat, 30 Apr 2005, Daniel Leidert wrote:
> 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 ass
Hello,
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-fr
6 matches
Mail list logo
