From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Alan Levy <alan.levy@plextek.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Problem using Subversion in Pyro
Date: Thu, 18 May 2017 16:14:18 +0300 [thread overview]
Message-ID: <026d9904-42bf-3314-24c9-dff2acc317cb@linux.intel.com> (raw)
In-Reply-To: <d0183f1a9e3742bc9dfca1a0b7a300b6@PLEXTEK-EXCH1.plextek.lan>
On 05/18/2017 04:04 PM, Alan Levy wrote:
> It does get built, and it apparently does get used to do the actual
> fetching, just not for miscellaneous functions such as populating
> SRCREV which rely on the svn executable being on the PATH. This
> appears to be deliberate since there is a FETCHCMD_svn variable in
> bitbake.conf. The simplest way for me to force an svn executable onto
> PATH was to add it to HOSTTOOLS but that may not be what is really
> intended.
SRCREV is supposed to be hardcoded in the recipe. What is the reason you
need to use svn to set it? Can you show how it's specifically done in
your recipe?
Alex
next prev parent reply other threads:[~2017-05-18 13:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 11:40 Problem using Subversion in Pyro Alan Levy
2017-05-18 12:40 ` Alexander Kanavin
2017-05-18 13:04 ` Alan Levy
2017-05-18 13:14 ` Alexander Kanavin [this message]
2017-05-18 13:32 ` Alan Levy
2017-05-18 13:46 ` Alan Levy
2017-05-18 13:47 ` Alexander Kanavin
2017-05-18 14:02 ` Alan Levy
2017-05-18 14:11 ` Alexander Kanavin
2017-05-18 14:24 ` Alan Levy
2017-05-18 13:00 ` Burton, Ross
-- strict thread matches above, loose matches on Subject: below --
2017-05-18 14:22 Alan Levy
2017-05-19 9:48 ` Richard Purdie
2017-05-19 9:57 ` Alan Levy
2017-05-19 10:09 ` Alexander Kanavin
2017-05-19 12:44 ` Alan Levy
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=026d9904-42bf-3314-24c9-dff2acc317cb@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=alan.levy@plextek.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.