Migrating Qt Crytpographic Architecture to KDE CVS

Justin Karneges justin-psi-A4HSxAr4s6pBDgjK7y7TUQ at public.gmane.org
Tue Sep 28 04:12:48 BST 2004

On Monday 27 September 2004 02:53 pm, Brad Hards wrote:
> On Sat, 25 Sep 2004 11:11 am, Brad Hards wrote:
> > Here is the short version of the plan (and there is no long version yet,
> > we'll make it up as we go along):
> >
> > 1. Justin makes up a tarball of the QCA part of his CVS tree and sends it
> > to me. Obviously it would be a bad idea to commit anything to that
> > version of QCA.
> > 2. I send it to the KDE CVS gods, and get them to unpack it in the
> > kdesupport module.
> > 3. In parallel, I'll update the website HTML, and get it installed
> > somewhere on http://developer.kde.org
> > 4. When the CVS tree is working on cvs.kde.org, I'll do a test commit (of
> > the unittest part, probably) and make sure it is all working. I'm
> > currently looking at how much it is going to take to get a Windows
> > version of Qt running locally, for testing.
> > 5. We announce the success to the world, and look for other people to do
> > work for which we can take credit :-)
> Steps 1, 2 and 4 are done. You can checkout kdesupport/qca now (or maybe
> later, if you are on anoncvs).

Yup, and there it is.

> I have a little bit of the HTML done, hopefully get it finished tonight.
> I've also created a qca component on http://bugs.kde.org, with myself as
> the default owner. Justin - do you want to be the owner? Or do you want
> them to go to a mailing list?

If you can use the Delta list, that would be great.  Let me know if I have to 
do anything on my end to make that work.


More information about the kde-core-devel mailing list