[Debian-med-packaging] [rt.broad #134078] Packaging IGV for Debian [PATCH]

Charles Plessy plessy at debian.org
Fri Jun 18 11:12:40 UTC 2010


Le Fri, Jun 18, 2010 at 09:11:36AM +0200, Andreas Tille a écrit :
> On Thu, Jun 17, 2010 at 11:01:40AM -0700, Shaun Jackman wrote:
> > Debian is divided up into its main repository and a non-free
> > repository. Without source code, maf.jar could be packaged in the
> > non-free repository, but it's definitely preferred to have the source
> > code.
> 
> That's actually not precise:  To be distributed via the Debian mirror
> network the existing source code is a precondition.  Without any source
> code a package will also not go into non-free.  The decision about
> official (main) Debian or non-free depends from the license of this
> source code.  If it is DFSG free it can go to main if it does not need
> any precondition from non-free.  In the later case it has to go into
> contrib.

Hi Andreas and Shaun,

I think that Andreas is confusing the request of having a source package with a
request of providing the sources. For instance the kernel ‘binary blobs’ and
the NVIDIA proprietary drivers do not provide sources, but exist in the
non-free section of our archive as source and binary package, where ‘source’
only means a package format that is used to build binary packages: the source
package can contain pre-compiled binary objects in the case of our non-free
section.

I have not CCed the IGV people, so that we do not create confusion until we
agree on our understanding of what are the requirements for non-free.

Also, in the case of maf.jar, the source package does not need to be a released
tarball: a checkout from the VCS where the code is (probably) located would be
enough to have the package in main (if the license is appropriate, of course),
provided that we can build maf.jar from this checkout.

Have a nice day,

-- 
Charles



More information about the Debian-med-packaging mailing list