Re: [Pkg-alsa-devel] RFS: alsa-tools
- To: debian-mentors@lists.debian.org
- Subject: Re: [Pkg-alsa-devel] RFS: alsa-tools
- From: Frank Küster <frank@debian.org>
- Date: Tue, 01 Feb 2005 10:41:58 +0100
- Message-id: <[🔎] 87r7k08vmh.fsf@alhambra.kuesterei.ch>
- In-reply-to: <20050131.221810.07640999.wlandry@ucsd.edu> (Walter Landry's message of "Mon, 31 Jan 2005 22:18:10 -0500 (EST)")
- References: <20050126181919.70693.qmail@web53204.mail.yahoo.com> <41F7FD2D.7040306@glocalnet.net> <ctgfj5$2ob$1@wonderland.linux.it> <20050131.221810.07640999.wlandry@ucsd.edu>
Walter Landry <wlandry@ucsd.edu> schrieb:
> "Marco d'Itri" <md@Linux.IT> wrote:
>> mikaelmagnusson@glocalnet.net wrote:
>>
>> >Do we have to split the alsa-tools source into two packages, one free
>> >and one non-free/contrib? It will make it a bit harder.
>> No.
>
> Unfortunately, that is not the case. All of the source for packages
> in main must satisfy the DFSG. For example, if there are some
> non-free, but distributable, files in the original tar ball, those
> have to be taken out and a new "original" tar ball made.
I don't have the original mails at hand, but IIRC the problem was that
some parts of the package _depend_ on something in non-free. In this
case, the split-off binary package would go to contrib, and the sources
can stay in main. If an upstream tarball contains code that is only
needed for compiling on M$ Windows, but is itself free, it can stay in
main as well.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Reply to: