Bugzilla Bug 47065

It's a very nice and smooth style for KDE 3.2, I think it should deserve a
ebuild as other styles and themes already do.

Reproducible: Always
Steps to Reproduce:

There is an ebuild available at
http://bugs.gentoo.org/attachment.cgi?id=27584&action=view as part of Bug 41111 

Created an attachment (id=29197) [edit]
activeheart-1.1.6.ebuild

x11-themes/activeheart ebuild

Created an attachment (id=29198) [edit]
activeheart-kwin-1.0.2.ebuild

x11-themes/activeheart-kwin

I posted the two ebuild, but I remember that in bug 40447 Brandon Hale said
that KDE-Look stuff wasn't things to be added to portage.
If KDE Styles can be added, I'll continue updating the ebuils, because I'm
"maintaining" them for http://flameeyes.web.ctonet.it/ (at the moment there is
a semi-outdated ebuild pack, tomorrow there will be a completely updated one :)
)

If so, why gtk engines should have space in Portage whilst Qt/KDE shouldn't?
Anyway, thanks for your ebuilds, I'll try them for sure! :)

Mostly because there's no developer who wants to sponsor supporting the themes
in portage.

And this is non-sense. A thing is a splash screen, a thing is a widget
theme/engine. If someone like Diego writes an ebuild for a KDE theme, there are
no reasons at all to do not include it in the Portage. It's not a stupid
wallpaper, it's something more "important"

If you feel so strongly about it, then I encourage you to become a developer
and spend your time working on KDE relate styles and themes.  Since there's
only a small handful of us that work on KDE stuff for portage, we could use the
help.

That's somethin I'd like to do! :) I only have to learn a bit better ebuilds
creation. But was I labelled as "non-sense" is to stop everything from
kde-look. I mean, if it's a wallpaper or a splash screen, it's obvious it
should be blocked. But in the case of a theme, well, it's not so obvious IMO.

Created an attachment (id=29405) [edit]
activeheart-1.1.7.ebuild

As I said, I'm maintaining these ebuild in my site, so I can continue uploading
them to bugs.gentoo.org if it's needed for version bumps and so on.
Actually, I'd prefere if I can continue using the same bug report (simpler to
remember) REOPENing it, one for package, but if you prefer one bug for update,
I need only to update the ebuild page with bug numbers :)

Definitely please continue to update this bug report with updated ebuilds!
thanks!

Created an attachment (id=29997) [edit]
activeheart-kwin-1.1.ebuild

Version bump

Created an attachment (id=29999) [edit]
activeheart-1.2.ebuild

Version bump

Created an attachment (id=30330) [edit]
activeheart-1.2.1.ebuild

Same thing that for bug #47501 : I'm already maintaining this package for my
ebuild pack, if someone can explain me what is needed to do, I can maintain it.

activeheart-1.2.1 and activeheart-kwin-1.1 commited

thanks you, Diego