RFC: Removal of KAutoConfig / KAutoConfigDialog
Benjamin Meyer
ben at meyerhome.net
Fri Oct 31 03:05:03 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 30 October 2003 9:53 pm, Matt Rogers wrote:
> On Thursday 30 October 2003 06:17 pm, Benjamin Meyer wrote:
> > On Thursday 30 October 2003 6:51 pm, Zack Rusin wrote:
> > > On Thursday 30 October 2003 18:17, Cornelius Schumacher wrote:
> > > > On Thursday 30 October 2003 17:52, Navindra Umanee wrote:
> > > > > It would be nice to see some documentation for kconfig_compiler to
> > > > > figure out the differences between the two... (sorry if I haven't
> > > > > found it)
> > > >
> > > > kconfig_compiler is orthogonal to kautoconfig. Its documentation is
> > > > in kdelibs/kdecore/kconfig_compiler/README.dox. It is also integrated
> > > > into the Doxygen generated API docs. See the docs of KConfigSkeleton.
> > > > If threre is missing something in the docs please tell us so that we
> > > > can fix that.
> > >
> > > Also, I just finished a tutorial. Will commit as soon as I finish
> > > something here.
> > >
> > > Zack
> >
> > After that is done then I guess just copy KAutoConfig* to all of the
> > apps/modules in cvs that need it and remove it from kdelibs?
> >
> > -Benjamin meyer
>
> Ideally all those apps/modules should be ported to the new kconfig_compiler
> stuff rather than duplicating tons of code all over CVS.
>
> Matt
Would this be a decition for the release manager? Keep the classes in cvs,
but mark them as volital or copy them all over cvs?
- -Benjamin meyer
- --
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE/odFi1rZ3LTw38vIRArAtAJ9mB1A57L0vm5QZyH92eHADKxSBJgCeLzBY
X5jAj02XTliSq6IKYT6EAMU=
=2w/9
-----END PGP SIGNATURE-----
More information about the kde-core-devel
mailing list