[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [MoM] mmseqs2



Hi Shayan,

On Mon, Jul 15, 2019 at 09:02:45PM +0100, Shayan Doust wrote:
> Well, it looks like the software compiles successfully and builds into a
> deb package.

Very good!
 
> Now, just a slight confusion within the debian/copyright file. Below is
> the current file that is incomplete.
> 
> > Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> > Upstream-Name: mmseqs2
> > Source: https://github.com/soedinglab/MMseqs2
> > Files-Excluded: lib/gzstream
> > Comment: The system-wide library (libgzstream-dev) supersedes that of the gzstream in lib/
> > 
> > Files: lib/zstd/*
> > Copyright: 2016-present Yann Collet, Facebook, Inc.
> > License: GPLv2

zstd is also packaged.  You can strip these files and Build-Depend
libzstd-dev.  There is no need to specify a copyright paragraph for
removed files.

> > Files: debian/*
> > Copyright: 2019 Shayan Doust <hello@shayandoust.me>
> > License: GPLv3
> 
> The issue I have is that, for instance, the library "cacode" falls under
> public domain. What would be written on the license file, if anything?

Here is an example:

    https://salsa.debian.org/med-team/ncbi-tools6/blob/master/debian/copyright

> Some of the years and contact information are missing on the copyright
> lines, as I don't have an idea as to when the license was instantiated /
> library was written and as to what contact email the author has. Would
> that be an issue in this state?

To be honest:  I "invent" something a year that sounds probable.  IMHO
this is some appropriate procedure to avoid serious software archeology.
 
> Also, looking at the headers of "alp", it seems to be licensed as
> "United States Government Work". As this doesn't seem to reflect a
> distinctive license, what is the approach for this?

I'd take the "PUBLIC DOMAIN NOTICE" as a good reason to declare it
as public domain.  Add the paragraph as Comment.
 
> Last thing, the "Files: data/*, examples/*, quinci/*, src/*, util/*,
> *.yml, *.md, *.txt, Dockerfile" line. I wasn't sure as to leave it as a
> wildcard "*" or use this means as I do not know what the licensing
> standpoint of something like this with multiple licenses due to
> libraries is.

The "Files: *" on top catches all files.  Than you list exceptions.
If you have no better clue for data/* etc. it can be assumed that
it is covered by "Files: *".
 
Now you are facing the not so fun since non-technical part of
Debian packaging. ;-)

Kind regards and thanks for your work on this

     Andreas.


-- 
http://fam-tille.de


Reply to: