During emerge for current stable version (0.99-r1) the following error is encountered: /bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -DLINUX -D__CPLUSPLUS -pthread -I/usr/include/FTGL -I/usr/include/freetype2 -O2 -march=k8 -pipe -MT init_cond.lo -MD -MP -MF .deps/init_cond.Tpo -c -o init_cond.lo init_cond.cc glConsole.cc:50:23: error: FTGL/FTGL.h: No such file or directory In file included from glConsole.cc:51: /usr/include/FTGL/FTGLPixmapFont.h:29:5: warning: #warning This header is deprecated. Please use <FTGL/ftgl.h> from now. glConsole.cc: In function 'int glConsoleDraw(gl_console_t*)': glConsole.cc:796: warning: passing 'double' for argument 1 to 'virtual bool FTFont::FaceSize(unsigned int, unsigned int)' media-libs/ftgl-2.1.3_rc5 is marked as stable for amd64 only - maybe this is a mistake as media-libs/ftgl-2.1.2 is ~ for all of the archs. In any case current situation is - 'stable' ftgl is not usable for 'stable' libprojectm, as the latter uses deprecated headers. I've checked and media-libs/libprojectm-1.1 is failing in the same way as 0.99. Feel free to recategorize this bug as lib-media/fgl-2.1.3_rc5 needs to be marked 'unstable on amd64 - I have no idea why it was marked stable in the first place, so this may be the most appropriate action after all Reproducible: Always
I have exactly the same problem on x86, as of today, merging media-libs/libprojectm-0.99-r1 against media-libs/ftgl-2.1.3_rc5, which I believe are the latest "stable" versions.
Can reproduce the bug here, using ftgl-2.1.3_rc5 on x86. Switching to libprojectm-1.1 gives the same error, only 1.2.0 compiles. (However, in my case libprojectm is probably some stale dependency by XMMS, which is long gone. Still annoying for those who usi the library.)
Please mark stable, =media-libs/libprojectm-1.2.0 =media-libs/libprojectm-qt-1.2.0 =media-plugins/libvisual-projectm-1.2.0 And media-sound/projectm-jack is optional for stabling or keywording.
amd64/x86 stable
(In reply to comment #3) > Please mark stable, > > =media-libs/libprojectm-1.2.0 > =media-libs/libprojectm-qt-1.2.0 > =media-plugins/libvisual-projectm-1.2.0 > > And media-sound/projectm-jack is optional for stabling or keywording. > What I mean that if you don't have all three packages, it doesn't make sense to have libprojectm at all -- it doesn't do anything without the -qt and libvisual plug-in. (It's a drop in runtime dependency for e.g. Amarok) If you don't want to keep maintaining it, just note it here. Thanks :)
alpha doesn't care, feel free to drop
(In reply to comment #6) > alpha doesn't care, feel free to drop Same for HPPA.
Broken ebuilds left the building.
The current keyword for split pkgs are ok. We have now audacious-plugins-2.0.0 in tree that can use only the libprojectm-1.2.0 without the split ones, so for this, your keywords are fine. When it will be request to stable you of course follow but I'm adding some missing ProjectM plugins from upstream and adding a meta ebuild for them which seems to make sense, multiple ebuilds in different categories, if this is the case, I'll open a KEYWORDREQ bug later on.