On Saturday 16 April 2011 11:37:14 am Ben Cooksley wrote:
> On Sat, Apr 16, 2011 at 1:22 PM, Ian Wadham <iandw...@gmail.com> wrote:
> > On Thursday 14 April 2011 11:53:17 pm Raphael Kubo da Costa wrote:
> >> I've just tried building a fresh new strigi clone here and everything
> >> worked fine:
> >>
> >>   $ git clone kde:strigi
> >>   $ cd strigi && mkdir build && cd build
> >>   $ cmake -DSTRIGI_SYNC_SUBMODULES=TRUE ..
> >
> > Tried  git clone kde:strigi, but some kind of no-access error.  So tried:
> >   git clone http://anongit.kde.org/strigi
> > got similar errors to those I got before and attached to my first email.
> >
> Can you please try using the git:// protocol instead of the http://
> protocol to clone the repositories? In the times I tried, I couldn't
> reproduce the errors that Git seems to be generating on your system.
> 
OK, thanks Ben, git clone git://anongit.kde.org/strigi, from the command
line, cloned strigi and all its subdirs successfully.

But '... http: ...' does not.  I am using bog-standard kdesrc-build-1.13,
as per http://techbase.kde.org/Getting_Started/Build/kdesrc-build.
That script uses http://anongit.kde.org/ as its default git repository
and, in my case, clones all the KDE libraries and modules except strigi.

So http: apparently does not work for cloning strigi.  My installation of
Firefox, networks, etc. is also bog-standard OpenSuSE 11.2 AFAIK.

This build stuff *ought to work as advertised*.  It is one of the "main
entrances" to KDE development for new developers or for old developers
like me who do not wish to do anything fancy, just build enough KDE libs, etc.
to be able to compile and build a KDE app with the latest libs, in this case
as preparation for nailing a problem with newer versions of Phonon, which
will no longer play my app's sounds as of KDE 4.6.

> I suspect either the version of git you have installed (which may be
> too old, I have v1.7.4.1) or alternately a proxy being inserted by
> your network provider which is interfering in the manner which git
> uses to perform access over http. Using the git:// protocol should
> avoid these proxies.
> 
So maybe kdesrc-build should use git:...etc. as its default repository,
rather than http:, and maybe the Getting Started pages need to specify
what versions of tools you need ...

All the best, Ian W.

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Reply via email to