- Package:
- ncbi-tools-x11
- Source:
- ncbi-tools6
- Description:
- NCBI libraries for biology applications (X-based utilities)
- Submitter:
- Sythos
- Date:
- 2017-12-01 16:12:03 UTC
- Severity:
- wishlist
Cn3D NCBI tools arrived to version 4.1 on site but 3.0 il packaged in SID
retitle 225651 ncbi-tools-x11: want Cn3D++ thanks Hi. Newer versions of Cn3D are part of NCBI's next generation toolkit (written in C++ rather than C), which I already intend to package (see http://bugs.debian.org/150636 ). However, I should warn you that this may not happen for a while, since the C++ Toolkit requires more effort to package due to its increased size and (limited) use of many additional libraries, and my current PC (a few years old) takes hours for each build attempt.
Hi,
since some time ncbi-blast+ is in testing.
Feel free to suggest further interesting software
Andreas.
Hi everybody,
its really that simple to close a bug which I'm doing here without a line
of code closing my first bug in this mail after having checked that zstd
has hit backports and adding "882244-done@bugs.debian.org" to the list of
receivers of this mail.
Not all bugs are *that* simple to solve but **everybody** is kindly
invited to head for the simple ones right now.
We should definitely try to fix the serious ones - even if they are mostly
not that simple.
Definitely.
Pinging Aaron explicitly to refresh his statement given several years ago.
Thanks for the fun and all your work
Andreas.
Andreas Tille <andreas@an3as.eu> writes: Hi, Andreas. Although Cn3D++ comes from the same overarching tree (NCBI's C++ Toolkit) as BLAST+, it is a separate project. The packaging work done for BLAST+ would make for a decent starting point, though. Meanwhile, what ever happened with https://bugs.debian.org/682042 ? ;-)
Hi Aaron,
Since as far as I know you are the team member with the best insight
into this code and your previous excuse that the build takes so long on
your machine should be not valid any more - would you volunteer to take
over this task?
Good question - but I think we should not mix to different issues in one
discussion. So I droped this bug from CC.
Kind regards
Andreas.