Kommander (also part of kdewebdev, developped by the quanta-team) is an editor and executor for .kmdr-files. This are xml-based gui-descriptions with embeded code. Since Kommander gets more and more popular, I think portage should provide am easy installation-routine for kommander-based applications (for the .kmdr's) to prevent wild growing .kmdr's everywhere in 20 different dir's This eclass is a first attempt of providing such functionality. Never the less there is some tuning nessesary where I don't know exactly how/if it can be done... It installes the .kmdr's in /usr/lib/kommander-apps/*.kmdr and create a little shellscript in /usr/bin which calles the interpreter with the .kmdr What do you thing about this in generel?
Created attachment 40234 [details] very basic eclass for kommander-based applications
Created attachment 40235 [details] example 1 using this eclass (frontend for locate/esearch)
Created attachment 40236 [details] example 2 using this eclass (extracts audiotracks from dvd's)
>Since Kommander gets more and more popular Your two examples are the first I'm aware of. If it will become helpful, why not. But please do not add something like need-kde(). Have a look at Bug 25013#c50 and Bug 58819 why.
I have another application that could make use of this eclasss: http://kqemu.sourceforge.net/
Well, if a dev wants to use this eclass, he's of course free to add it to portage. You might want to post it on a wider forum, although it's a simple eclass so there might not be much interest. Any way, a bugreport requesting an eclass doesn't make sense, so I'm closing this. You can submit ebuilds in a bugreport, or you can include the eclass with your ebuilds if they're outside portage.