RFC: Removal of KAutoConfig / KAutoConfigDialog

[Rob Kaper]

On Thu, Nov 13, 2003 at 09:24:18AM -0500, Benjamin Meyer wrote:
> > a) KAutoConfig is so broken that these ports are necessary and justified,
> > in which case we should not release KDE with Kopete using that broken
> > KAutoConfig.
> 
> Where did this come from?  KAutoConfig isn't broke at all, it is simply being 
> replaced with something that does more.
> 
> > b) We don't mind Kopete using KAutoConfig because it's not broken, in which
> >    case porting to KConfigDialog cannot be justified because of the feature
> >    freeze.
> >
> > Rob
> 
> This was already discussed in a previous thread.  Porting anything in cvs 
> to/from KAutoConfig/KConfig_XT shouldn't happen in cvs currently as it is 
> frozen.

a) came from Waldo's intention to port this still while in the freeze, which
would mean it's a bug fix. So it simply looks like we agree on b).

Rob
-- 
Rob Kaper     | "In the name of sheer pity, won't someone operate on
cap at capsi.com | Chairman Arafat and put that poor cancer into a cleaner
www.capsi.com | environment? -- Rick Brookhiser
-------------- 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/20031113/4e387d64/attachment.sig>