blahah / transrate

Understand your transcriptome assembly
http://hibberdlab.com/transrate
Other
100 stars 34 forks source link

transrate Debian packaging #160

Open mr-c opened 9 years ago

mr-c commented 9 years ago

Oh my, 16 dependencies! Alas the biggest delay will be waiting for leaf packages to be accepted so those packages that depend on them can be sent in.

Dependencies that need packaging (default) or updates (as marked):

[ ] transrate
 + [x] transrate-tools
 + [x] salmon
 |  + [x] libcereal-dev
 |  + [x] libgff-dev
 |  + [x] libspdlog-dev
 |  + [x] libjellyfish-2.0-dev (update)
 |  + [x] libbwa-dev (update)
 + [x] snap-aligner
 + [x] ruby-crb-blast
 |  + [x] ruby-threach
 |  + [x] ruby-fixwhich
 |  |  + [x] ruby-pathname2
 |  |  |  + [x] ruby-facade
 + [x] ruby-fix-trinity-output
 + [x] ruby-yell
 + [x] ruby-colorize (update from 0.7.3 to 0.7.7)

http://anonscm.debian.org/cgit/debian-med/cereal.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800335 https://ftp-master.debian.org/new/cereal_1.1.2-1.html http://tracker.debian.org/pkg/libcereal

http://anonscm.debian.org/cgit/debian-med/libgff.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800336 https://ftp-master.debian.org/new/libgff_1.0-1.html https://packages.qa.debian.org/libg/libgff.html

http://anonscm.debian.org/cgit/debian-med/spdlog.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800337 https://ftp-master.debian.org/new/spdlog_1.4-1.html https://tracker.debian.org/pkg/spdlog

http://anonscm.debian.org/cgit/debian-med/jellyfish.git

http://anonscm.debian.org/cgit/debian-med/bwa.git https://ftp-master.debian.org/new/bwa_0.7.12-5.html

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800339 http://anonscm.debian.org/cgit/debian-med/salmon.git https://ftp-master.debian.org/new/salmon_0.4.2+ds1-1.html https://tracker.debian.org/pkg/salmon

http://anonscm.debian.org/cgit/debian-med/snap-aligner.git http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800340 https://tracker.debian.org/pkg/snap-aligner

http://anonscm.debian.org/cgit/debian-med/transrate-tools.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800412 https://ftp-master.debian.org/new/transrate-tools_1.0.0-1.html https://tracker.debian.org/pkg/transrate-tools

Ruby packages: https://wiki.debian.org/Teams/Ruby/Packaging

https://anonscm.debian.org/cgit/pkg-ruby-extras/transrate.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800733

https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-fix-trinity-output.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800489 https://tracker.debian.org/pkg/ruby-fix-trinity-output

https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-yell.git http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800494 http://tracker.debian.org/pkg/ruby-yell

https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-threach.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800734 https://ftp-master.debian.org/new/ruby-threach_0.2.0-1.html https://tracker.debian.org/pkg/ruby-threach

https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-crb-blast.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800737 https://ftp-master.debian.org/new/ruby-crb-blast_0.6.4-1.html https://tracker.debian.org/pkg/ruby-crb-blast

https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-pathname2.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800740 https://ftp-master.debian.org/new/ruby-pathname2_1.7.4-1.html http://tracker.debian.org/pkg/ruby-pathname2

https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-fixwhich.git http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800742 https://tracker.debian.org/pkg/ruby-fixwhich

https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-facade.git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800488 https://ftp-master.debian.org/new/ruby-facade_1.0.7-1.html

https://tracker.debian.org/news/718538

mr-c commented 9 years ago

This will be a five-phase submission:

1) transrate-tools, snap-aligner, ruby-fix-trinity-output, ruby-yell, libcereal-dev, libgff-dev, libspdlog-dev, libjellyfish-2.0-dev, libbwa-dev (update), ruby-facade, ruby-colorize (update from 0.7.3 to 0.7.7), ruby-threach 2) salmon, ruby-pathname2 3) ruby-fixwhich 4) ruby-crb-blast 5) transrate itself

blahah commented 9 years ago

@mr-c this is heroic! And very much appreciated. What can we do to support it?

mr-c commented 9 years ago

@Blahah Thanks :-) The licenses need clarifying, see https://github.com/Blahah/transrate/issues/159.

In general it seems that the Ruby community is a fan of the MIT license and not putting this in each file nor having a copyright line. Alas this is rather confusing as multiple versions exist, all with the same name. When documenting the license for Debian I can use the short name 'expat' if it exactly matches that variant; otherwise it creates a delay.

Ideally the program licensecheck (from the devscripts package) would give me the correct information when scanning source trees.

(sid)255 mcrusoe@localhost:~/debian/transrate-tools$ licensecheck `git ls-files`
src/bam-read.cpp: *No copyright* UNKNOWN
src/bam-read.h: *No copyright* UNKNOWN
src/pileup.cpp: *No copyright* UNKNOWN
src/pileup.h: *No copyright* UNKNOWN
src/segmenter.cpp: *No copyright* UNKNOWN
src/segmenter.h: *No copyright* UNKNOWN
blahah commented 9 years ago

Can I deal with that by just putting a LICENSE file in the repo (see https://github.com/Blahah/transrate-tools/commit/215f661ac19fe847da62f49f56e6b3599aa81b72)?

mr-c commented 9 years ago

For transrate-tools & #159 yes, that is required; thanks!

A copyright line in each file would be nice too.

blahah commented 9 years ago

You're right, I never put the license in every file because I find it aesthetically unpleasant - a distraction from the pure utility of the code. But now that you mention it, I see why it would be useful!

Is there some convention for stating the license/copyright as simply as possible?

mr-c commented 9 years ago

:-)

I know of no convention, alas. Some licenses give specific guidance on how to use them in a source file; many do not.

For the MIT family of licenses it appears that the best bet is to include the entire license in the header as it is unversioned and so short. See: https://anonscm.debian.org/cgit/collab-maint/devscripts.git/tree/scripts/licensecheck.pl#n593

(DIB lab had the same issue with the BSD license; I ended up adding the full text of the license to every file during a copyright/license audit brought about because seqan didn't declare all of its constituent copyrights and licenses)

blahah commented 9 years ago

Putting the whole MIT license in seems horrible. Would a two-liner like this suffice?

# Copyright Richard Smith-Unna and Chris Boursnell 2015. This file is MIT licensed.
# Full license at: https://github.com/Blahah/transrate/blob/master/LICENSE
blahah commented 9 years ago

Because honestly I'd rather just waive all rights in a short one-liner than have a big header in every file! I would feel sick every time I saw it!

mr-c commented 9 years ago

:-)

This variation allows both the copyright and license to be detected:

mcrusoe@localhost:~$ cat test.py
#!/usr/bin/env python
# Copyright 2015 Richard Smith-Unna and Chris Boursnell.
# This file is MIT licensed.
# Full license at: http://opensource.org/licenses/mit-license.php

import this
mcrusoe@localhost:~$ licensecheck --copyright test.py 
test.py: MIT/X11 (BSD like)
  [Copyright: 2015 Richard Smith-Unna and Chris Boursnell]
blahah commented 9 years ago

OK, deal ;).

mr-c commented 9 years ago

@Blahah https://wiki.debian.org/Teams/Ruby/RubyExtras/UpstreamDevelopers :-)

mr-c commented 9 years ago

Transrate-tools has been accepted into Debian! https://tracker.debian.org/pkg/transrate-tools

mr-c commented 8 years ago

snap-aligner has been accepted: https://tracker.debian.org/pkg/snap-aligner

I've received a series of apologies from a debian-ruby team member apologizing for the delays in reviewing my ruby packages.

mr-c commented 8 years ago

I'm preparing the salmon package (0.4.1) and I see that version 0.6 is out. @Blahah, when do you expect transrate to be updated to handle the format changes?

blahah commented 8 years ago

@mr-c we'll push a small patch soon addressing reviewer's comments, after which the next release will support the latest salmon. I guess late feb.

Thanks for all your hard work on this :)