RFC: remove qt-copy

[Michael Pyne]

On Monday 25 May 2009 23:04:46 Michael Pyne wrote:
> On Monday 25 May 2009 22:19:35 Aaron J. Seigo wrote:
> > On Monday 25 May 2009, Michael Pyne wrote:
> > > > It means checking out and building Qt again.
> > >
> > > It is not (yet) supported by kdesvn-build. ;)
> >
> > good point. any timeline on such a thing? :)
>
> Well I should probably release 1.9 first since I've been promising it would
> be "Real Soon Now" for about 6 weeks now.

The initial version of kdesvn-build supporting Qt from git is ready.  Due to 
the impending 4.3 release I'm performing the work in a branch though, (aptly 
named kdesvn-build-1.10 in /branches/work).

I've merely observed it download Qt using git and start into the configure 
script, although from that point on there shouldn't be much different for the 
actual build.

You can download a different repository (i.e. the kde-qt one) by specifying the 
repository name using the repository option for qt-copy.  i.e.

module qt-copy
 repository +kde-developers/qt/kde-qt.git
 ...
end module

Even if you don't use kde-qt and  use vanilla Qt you should keep the module 
name as qt-copy for now.  apply-patches is a useless option now from what I 
can tell so it's gone.

And so far the configure script looks like it's stuck in an infinite loop for 
me. :-/

Hopefully it's not related to srcdir != builddir but I don't have time to look 
at it now, hopefully I will tomorrow.

Regards,
 - Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090603/f384e005/attachment.sig>