fftw3 introduced new API (and header & library files have different names). Therefore, it should be a separate ebuild. Otherwise, ebuilds that depend on (old) fftw will fail when fftw upgraded to >= 3.0. Reproducible: Always Steps to Reproduce:
That's what SLOTs are for, side-by-side installations. fftw-3 does not remove fftw-2. donnie@supernova donnie $ grep ^SLOT /usr/portage/dev-libs/fftw/fftw-* /usr/portage/dev-libs/fftw/fftw-2.1.3-r1.ebuild:SLOT="2.1" /usr/portage/dev-libs/fftw/fftw-2.1.5-r1.ebuild:SLOT="2.1" /usr/portage/dev-libs/fftw/fftw-2.1.5.ebuild:SLOT="2.1" /usr/portage/dev-libs/fftw/fftw-3.0.1.ebuild:SLOT="3.0"
What's good is this for if e.g. media-gfx/grace depends on fftw? ( >=dev-libs/fftw-2.1.3 ) and hence will happily try to build (and fail using FFTW) if fftw-3.01 is installed?!
Then this is a bug for grace, not for fftw. Re-assigning and changing summary.
Why then there are e.g. separate dev-libs/hdf and dev-libs/hdf5?
I wish there wasn't. That's a broken dependency. It should be done in the same way as gtk+-1 and gtk+-2. I've fixed this.