> On 2/8/07, Ciaran McCreesh <[EMAIL PROTECTED]> wrote: >> On Thu, 8 Feb 2007 10:38:08 +0100 Jose San Leandro >> <[EMAIL PROTECTED]> wrote: >> | A friend of mine and myself are willing to develop some tools to help >> | ebuild development. >> >> All the common cases should be handled by default functions, package >> manager functions and eclasses. Thus, writing ebuilds should consist >> merely of handling unique or uncommon special cases, and the best tool >> for doing that is an ebuild-aware text editor. >> Christopher Covington wrote: > Apropos ebuild-aware text editor, has anyone written an eclipse plugin > yet? I find that setting up ebuild as an external tool is basically > all I need but syntax highlighting and eclass reference would make > things prettier. > Personally I find kwrite or kate to be excellent. I guess kate if you want to set up tools etc. Have looked at the bash syntax highlighting xml for katepart in (~|/usr/share)/apps/katepart/ and it's an excellent basis. Am hacking it now to add ebuild functions, but if anyone knows a bit more about this (specifically writing rules) and is willing to help, please mail me.
-- gentoo-dev@gentoo.org mailing list
