There is one thing i just don´t get over with.

There are several modules overwriting XOOPS core files. How does this concept work. I mean basicly every module overwriting a corefile would crush other modules which already have overwritten the same corefiles themselves with what they need.

How should someone follow up whats going on?
Running a diff before every installation on every file and add these differences to the existing corefile?
Documention for many modules in this regard is non existent.

I mean there must be some other way, doesn´t it?

I´m no programer, at least the last thing i did was coding a Laserbikes (Tron) game more then 10 years ago in Turbo Pascal 6. :)


For relation to Quality assurance which should start in the future ... will any module overwriting corefiles for that matter pass QA process?

Which modules do that? I haven't seen that many modules, but yet to find any, which adds or modifies core files (quite common in PostNuke, though)

No, those modules would not pass QA process, I think - at least, they shouldn't.

First thing comes to my mind:

Invision Powerboard as a moduleversion for xoops.

For other i have to dig but the thought of my first post always strikes me when i upload a module and my ftp program asks for permission to overwrite a file whatsoever.

IPB for XOOPS is special because it needs core changes to function properly.

Since this is a rather special module, I wouldn't be too concerned about it being a normal occurrence