[oe] SVN fetcher behaviour

Hans Henry von Tresckow hvontres at gmail.com
Fri Oct 5 17:02:27 UTC 2007


On 10/5/07, Philippe De Swert <philippedeswert at scarlet.be> wrote:
>
> Hello all,
>
> On Thu, 2007-10-04 at 11:57 +0100, Martyn Welch wrote:
> > It is failing to download gconf-dbus using "gconf-dbus_svn.bb". It seems
> > that the script does not specify a revision and it therefore trying to
> > download revision 1. This fails.
> >
> > I have managed to get the script to continue buy hacking the script to
> > get it to download the current revision (608), by adding "rev=608" to
> > the SRC_URI.
>
> I ran into a similar problem recently and it seems you need to edit
> ../org.openembedded.dev/conf/distro/include/sane-srcdates.inc or make
> sure it is included in your distro.
>
> > I've looked at
> > http://www.openembedded.org/user-manual&dpage=src_uri_variable, which
> > (under "SVN") describes the behaviour of the svn fetcher. This doesn't
> > seem to specify what the default behaviour of the svn fetcher is when no
> > revision is specified, I'd assumed it would be the "head", though I am
> > now having some doubt.
>
> I think this should be the default behaviour, unfortunately it is not.
> The expected behaviour is fetch the latest revision and build it but it
> dies not.  I think ib general it is a great improvement for managing svn
> revisions, but it sucks at building the latest and newest.
>
> Cheers,
>
> Philippe
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
<http://bugs.openembedded.org/show_bug.cgi?id=2897>

The default of "1" is set in conf/bitbake.conf. The reason for this is that
any svn recipe without an explicit SRCREV set will cause parsing to fail if
the build machine or the svn server is off line. If you can live with this
limitation, then you could comment that line out to get the default
behavior.



-- 
Henry von Tresckow (hvontres)



More information about the Openembedded-devel mailing list