Summary: | Please keyword and stabilize media-libs/libprojectm 1.2.0 and related ebuilds | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Konrad Karczewski <konrad.karczewski> |
Component: | [OLD] Library | Assignee: | Gentoo Sound Team <sound> |
Status: | RESOLVED LATER | ||
Severity: | normal | CC: | ppc64, ppc, serkan, sparc |
Priority: | High | Keywords: | KEYWORDREQ, STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Konrad Karczewski
2009-03-09 12:44:57 UTC
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. |