[Development] Qftp removal
thiago.macieira at intel.com
Tue Apr 3 23:33:59 CEST 2012
On terça-feira, 3 de abril de 2012 20.10.08, shane.kearns at accenture.com wrote:
> Ok, there are three options I can see and we need to choose one.
> 1. One add-on for each removed API (e.g. qftp.git, qhttp.git)
> 2. One add-on for each module (e.g. qt4network.git)
> 3. A catch-all kitchen sink repository (e.g. qt4support.git)
> We promised this when removing the APIs, and again in the Qt5 alpha
> announcement. The code needs to be available by the time we release the
> Each API builds as a separate (static) library using only public exports of
> Qt5. (QHttp has a renamed private copy of QAuthenticator and QRingBuffer)
Go for option 1.
It's not any more effort than the others, unless we decided to build one single
library (which isn't what you said).
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/development/attachments/20120403/24b17de7/attachment.bin
More information about the Development