Three new Bioinformatics packages, just version bumps

I just used the existing 1.4.10 goolf toolchain that was already used for previous versions and bumped to the newest version that compiled cleanly.

I plan to work on migrating these to a newer gcc based toolchain.

Not sure if the commits should be cleaner.
Hi Robert,

Supposedly, this issue was opened for this exact reason:
https://github.com/hpcugent/easybuild-easyconfigs/issues/383

When you mentioned Boost, you basically hit the nail in the head:
the most tricky aspect is to find the common set of `biodeps` which allows
the majority of these tools to be built; Boost is a notoriously tricky one to get right
(mainly because backwards-compatibility is specifically NOT one of the objectives of that library).

If you have a proposition about massive updates of the bioinformatics packages
(which inevitably will happen sooner or later) please follow up under that thread.

As regards who may be interested, look at some possible perpetrators, over here:
http://f1000.com/posters/browse/summary/1094822

Now, that being said, here is my wishlist of what should be the next objective (pipedreaming=true):
* @pescobar 's PRs are tested and merged to the maximum extent possible;
  AFAIK, these are all bioinformatics-related and quite common needs
* Whatever else can easily be included from Elements of Bioinformatics, it should:
  http://elements.eaglegenomics.com
* some minor other PRs (like #568) should also be merged, to prevent duplication of work
* Finding recent sets of (Perl, Python, Java, Boost...) and (gnu, intel) toolchains; that is going to be
  the holy grail of this business. Esp. `gnu` vs `intel` compatibility may permit big user advantages
  and uniform experience across different environments (hpc, grid, cloud, clusters, desktops...)!
* If all above are done in a reasonable manner, serving a number of sites, this will be updated:
  http://hpcbios.readthedocs.org/en/latest/HPCBIOS_2012-94.html#hpcbios-2012-94

If I was you, I would start with `eb --from-pr <prnumber>` on PRs of Pablo, so that things get tested a little bit (the more SUCCESS codes there are there, the higher the probability to get them in).

If you are interested in this, I suggest to hijack one of the easybuild hangouts (more specifically, the time right *after* the regular agenda) in order to put our thoughts together about next steps.
Almost certainly, this would end up into an "online hackathon week" to do a massive cleanup of existing PRs and updating builds to fresher versions (of sources & compilers).

'nough said... F.