I think that lastfm ebuild should have a static useflag because some people (like I) don't want to compile qt just for 1 application. If you would enable the static useflag then lastfm would install a linux binary statically linked to qt but if you wouldn't enable that useflag then the ebuild would require qt. If somebody doesn't like that approach the there is an other - making a "lastfmplayer-bin" ebuild but this isn't that good (imho). (there is a working ebuild in bug #102059)
(In reply to comment #0) > I think that lastfm ebuild should have a static useflag because some people > (like I) don't want to compile qt just for 1 application. If you would enable > the static useflag then lastfm would install a linux binary statically linked > to qt but if you wouldn't enable that useflag then the ebuild would require qt. > Even with a static useflag it would still require qt-4.1 to be installed in order to build the package. All it would mean is that qt is not required at runtime.
Maybe then a "qt" useflag?
binary-ebuilds have all sorts of problems. I am not planning to add one in the close future. However you can find one in some overlays, for example the zugaina one: emerge layman echo "source /usr/portage/local/layman/make.conf" >> /etc/make.conf layman -f -a zugaina emerge -va lastfm-bin good luck :)
It appears that Comment #1 and Comment #2 are due to a misunderstanding in Comment #0 When gentoo offers a choice between a binary package (from upstream) and a source pacakge, there are 2 seperate packages. For example, openoffice-bin vs openoffice, azureus-bin vs azureus. This is done by the package name, NOT by use flag. Comment #0 is correct in that the precompiled static binary from upstream does not require qt. However, this is refuted by comment #3, "binary-ebuilds have all sorts of problems"
Closing.
