Release Criteria

[Lubos Lunak]

On Friday 15 November 2002 06:32, George Staikos wrote:
> On November 14, 2002 16:02, Ian Reinhart Geiser wrote:
> > On Thursday 14 November 2002 03:46 pm, Harri Porten wrote:
> > > On Thu, 14 Nov 2002, Ian Reinhart Geiser wrote:
> > > > > - Binary compatibility is preserved
> > > >
> > > > Do we have an automated way of testing this?  It would be great to
> > > > have a make bctest to run when we are doing changes here local.
> > >
> > > Unless someone else has something ready: I have an idea and was going
> > > to come up with a proof-of-concept implementation anyway. Might require
> > > some am_edit or unsermake support to be practical.
> >
> > i have been olaying arround with nm and ldd but so far have nothing
> > reliable. The big problem is we need to have a binary linked against an
> > older kdelibs, and for the sake of portabilty i dont know how to do this?
>
>   We could just record the symbols and other information in a big data file
> after each release and use that for comparison, right?

 Yes. But just using 'nm' and 'ldd' is not enough, as this would catch 
problems with missing/changed functions, but not changes in structures 
layout. I think the script would also have to parse all installed .h files 
(think about things like new virtual methods, changed base class or swapped 
order of two vars in the class).

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/