strigi in ebn

[Allen Winter]

On Wednesday 07 March 2007 4:04:09 am Adriaan de Groot wrote:
> [[ cc'ing -quality, which is the best list for code-quality-checking things ]]
> 
> On Wednesday 07 March 2007 08:19, you wrote:
> > Kun je strigi weer opnemen in de apidocs- en codecheck?
> 
> i18n("Can you re-add strigi to the apidox and code checking?")
> 
> Yes, I can, but it will take until next week at least since I'm swamped with 
> other stuff and have to re-remember how to do it. Maybe Allen can do it, if 
> he's not torn up with PIM release stuff.
>
It should have happened automatically as I setup all our EBN quality tools
to run on kdesupport a couple weeks ago.

The problem:  our tools assume a component/module/subdir hierarchy;
where for example component=kde-4.0, module=kdepim, subdir=kmail.
But kdesupport doesn't follow that layout: kdesupport is a module and
needs to be logically moved into some component... just like we did
by putting koffice and kdevelop into a "bundled-apps" component.

In summary: kdesupport isn't a separate component, it is a module.
kdesupport must be relocated under an existing component (kde-4.0, I think)
or we need to create a new component (misc?) for it.  



-- 
KDEPIM Developer
I accept PayPal payments to awinterz at earthlink.net