From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Ignore externals from a SVN source in SRC_URI
Date: Mon, 04 Apr 2011 19:44:20 -0700 [thread overview]
Message-ID: <4D9A8204.1030908@gmail.com> (raw)
In-Reply-To: <4D997896.9050607@gmail.com>
On 4/4/2011 12:51 AM, Francois Retief wrote:
> Hello,
>
> What is the recommended way to ignore external directories from a SVN
> source? Tried SVNCOOPTS, but it did not work.
>
yes it could mislead thats why. Since it wont update external svn repos
when you change SRCREV it will give false information of updating all
thats checked out.
> So I hacked bitbake for my needs with the patch below. But is there a
> better way?
>
This seems ok
> SRC_URI =
> "svn://svn.somesite.com/trunk;module=somemodule;externals=ignore;proto=https"
>
> Cheers
> Francois
>
> diff --git a/lib/bb/fetch/svn.py b/lib/bb/fetch/svn.py
> index ba9f6ab..f22f572 100644
> --- a/lib/bb/fetch/svn.py
> +++ b/lib/bb/fetch/svn.py
> @@ -114,6 +114,12 @@ class Svn(Fetch):
> if command is "info":
> svncmd = "%s info %s %s://%s/%s/" % (basecmd, "
> ".join(options), proto, svnroot, ud.module)
> else:
> + if "externals" in ud.parm:
> + if ud.parm["externals"] == "ignore":
> + options.append("--ignore-externals")
> + else:
> + raise FetchError("Invalid value for 'externals':
> expected 'ignore'")
> +
> suffix = ""
> if ud.revision:
> options.append("-r %s" % ud.revision)
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2011-04-05 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 7:51 Ignore externals from a SVN source in SRC_URI Francois Retief
2011-04-05 2:44 ` Khem Raj [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D9A8204.1030908@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox