KDE ABI stability?

[Brad Hards]

On Wednesday 07 December 2005 07:12 am, Maks Orlovich wrote:
> On Tuesday 06 December 2005 14:56, Brad Hards wrote:
> > On Wednesday 07 December 2005 06:48 am, Leo Savernik wrote:
> > > Am Dienstag, 6. Dezember 2005 00:13 schrieb Nicolas Goutte:
> > > > > This situation just craves for a pre-commit tool that keeps any
> > > > > malicious commits from ever hitting rcs.
> > > >
> > > > Even the smartest tool will not be enough (not counting the runtime
> > > > that it would need on the KDE SVN server).
> > >
> > > For C++-ABI checking, a tool would be enough. For behavioural checking,
> > > it certainly wouldn't be feasible.
> >
> > If someone has such a tool, I can run it on the outputs of the buildbot.
> > It might not be very useful now, but as KDE4 stablises, it may become so.
> > It would also be nice to get it working correctly and acceptably fast
> > when it doesn't matter so much.
> >
> > Anyone?
>
> make bcheck, as long as you use automake and not unsermake.
automake and KDE4 aren't a happy combination for me.

Brad
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051207/78e95c58/attachment.sig>