* dinges:
  Drop to 1.49.1 for GObject-Introspection (else needs newer glib)
  Add SWIG/3.0.8 for Python/3.5.2 and intel/2016b
  Add pixman/0.34.0 for intel/2016b
  Pango/1.40.3 for intel/2016b
  Cairo for intel/2016b

fix source URL in GCCcore 6.2.0 easyconfig

bump version to 3.0.0.dev0

{cfd} [dummy] FLUENT/17.1

{tools}[dummy/dummy] EasyBuild v2.9.0

release EasyBuild v2.9.0

bump version to 2.9.0 & update release notes

LeadIT 2.1.9

This reverts commit d470e60f.

Use the correct configure option to use the internal libxml.
And keep the dependencies as close to the normal tool-chain versions as
possible.

dependency on a dummy-toolchain gettext instead of a run time dependency
on a toolchain gettext.

Add required dummy toolchain versions of gettext-0.19.6 and .7

The original problem is that when building libxml2 on a system with
liblzma installed by the distro, it picks up dependencies on lzma
routines. Some of the versions of Gromacs are linking against libxml2
statically, causing link errors agains lzma. And any other software that
does static linking against libxml2 will have the same problem.

There is a cyclic dependency between XZ, libxml2, and gettext.
Fix this by adding a dummy toolchain build of gettext without any
dependencies on anything.

XZ for the updated toolchains are then built with the
dummy-toolchain gettext as a build dependency.
And then normal toolchain builds of libxml2 (now with XZ dependency) and
gettext can be built against that XZ.

This was originally discussed in issue #3408.

{vis}[foss/2016a,intel/2016a] ParaView v4.4.0, ParaView v4.4.0

{lang,lib}[GCC/4.8.4] Python 2.7.9 (bare) + libxml2 2.9.2

add easyconfig libibmad-1.3.12-GCC-4.9.3-2.25.eb, add easyconfig libibumad-1.3.10.2-GCC-4.9.3-2.25.eb