--nextPart1584547.FDjrY7JW9d
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Saturday, 2009-10-17, Thiago Macieira wrote:
> Em S=E1bado 17. Outubro 2009, =E0s 13.44.39, Kevin Krammer escreveu:
> > On Friday, 2009-10-16, Thiago Macieira wrote:
> > > Em Sexta-feira 16. Outubro 2009, =E0s 17.32.16, Kevin Krammer escreve=
u:
> > > > On Friday, 2009-10-16, Thiago Macieira wrote:
> > > > > Em Sexta-feira 16. Outubro 2009, =E0s 08.50.19, Kevin Krammer=20
escreveu:
> > > > > > On Friday, 2009-10-16, Thiago Macieira wrote:
> > > > > > > Em Quinta-feira 15. Outubro 2009, =E0s 23.53.18, Chani escrev=
eu:
> > > > > > > > so if there *is* a way for people to set up their git
> > > > > > > > repository so that it automagically updates to the latest
> > > > > > > > recommended qt with just a 'git pull' or whatever, can we
> > > > > > > > have instructions for that please?
> > > > > > > >
> > > > > > > > :)
> > > > > > >
> > > > > > > There is a way, provided you never have commits of your own on
> > > > > > > top.
> > > > > > >
> > > > > > > git fetch origin HEAD
> > > > > > > git reset --hard FETCH_HEAD
> > > > > >
> > > > > > So if I do that now or right after a clone, do I have to repeat
> > > > > > it before every update or does this make the KDE branch
> > > > > > permanently work the way it is intended?
> > > > >
> > > > > When you clone, you get the branch that HEAD points to.
> > > > >
> > > > > But then you are at that branch. If HEAD points somewhere else, y=
ou
> > > > > won't know. You need to run these commands above for every update.
> > > >
> > > > Ok, thanks. Clone it is then.
> > > > As a bonus it removes the need for make confclean :)
> > >
> > > Please don't.
> >
> > Relax, I won't do that every time :)
> > Just when the requirement of KDE makes the current checkout useless due
> > to this weird limitation.
> >
> > > A clone is a 170 MB transfer. A fetch is usually just a few kilobytes
> > > -- at most 5 MB when I push a new release.
> >
> > Yeah, I noticed.
> > But 170MB every several months is acceptable, even if it takes quite a
> >  while.
>=20
> Right. You'll do a 170 MB transfer when a 0 MB transfer is enough.
>=20
> How is that acceptable?

I didn't claim that it is perfect, but it beats rebuilding Qt and kdesuppor=
t=20
twice because updating Qt did not actually update it.

As I said I do a clean build (including prior removal of build and install=
=20
dirs) whenever updating Qt so the time needed for getting these 170MB don't=
=20
add that much overhead.

Developers who do not do that might be faster searching list archives and/o=
r=20
blogs for finding the branch of the day to switch to.

We all know that the ideal solution (i.e. neither download nor build overhe=
ad)=20
would be to use the devel packages of our distributions.

Cheers,
Kevin
=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart1584547.FDjrY7JW9d
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQBK2erTnKMhG6pzZJIRAq81AJ9TaRul1nYcPQh1HkR7bBqYddahfwCdEO+h
AIldcstQuB2CboL94jT0gR4=
=lNkm
-----END PGP SIGNATURE-----

--nextPart1584547.FDjrY7JW9d--