From: Denys Dmytriyenko <denys@ti.com>
To: Paul Kovitz <paul.kovitz@welchallyn.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: Updated Core TI-SDK setup and build instructions
Date: Fri, 14 Jun 2013 12:31:52 -0400 [thread overview]
Message-ID: <20130614163152.GA7791@edge> (raw)
In-Reply-To: <CA+edY+S1cuYX1c7XJU5K13mRUXcNu+XcL7KsEPFOTSCKA7kn0g@mail.gmail.com>
On Fri, Jun 14, 2013 at 09:27:18AM -0700, Paul Kovitz wrote:
> I see the metadata file revisions are locked down. Still I have questions.
>
> I ran the oe-layertool-setup.sh script but still there are recipes, the
> ltp-ddt .bbappend files in
> sources/meta-arago/meta-arago-distro/recipes-devtools/ltp-ddt, that have
> SRCREV = "{AUTOREV}".
>
> I expected the automatically generated local.conf to contain something like
> SRCREV_pn-ltp-ddt = "70e324b8352e817485cc5e6865341c1a40118f78" (or some
> such SHA1) so I know I build the same ltp-ddt that was used to generate the
> SDK.
Yes, ltp-ddt is still AUTOREV-ed, unfortunately. But it is a test tool anyway
and should not be part of the production system... We should probably look
into pinning it as well for the releases - all other packages are pinned, as
far as I know.
> Did I miss a step? Is there a configuration file somewhere else I did not
> find? To get the sources for the bitbake metadata, I ran
>
> git clone git://arago-project.org/git/projects/oe-layersetup.git amsdk
> cd amsdk
> /oe-layertool-setup.sh -f configs/amsdk/amsdk-05.07.00.00-config.txt
>
> Also, in meta-arago-extras/recipes-connectivity/wpa-supplicant/
> wpa-supplicant_r5.00.18.bb,
> meta-arago-extras/recipes-connectivity/wpa-supplicant/
> wpa-supplicant_r5.sp4.01.bb,
> meta-arago-extras/recipes-bsp/ti-compat-wireless/
> ti-compat-wireless-wl12xx_r5.sp4.01.bb and
> meta-arago-extras/recipes-connectivity/hostap/hostap-daemon_r5.00.18.bbthere
> are SRCREV = "git tag" instead of a SHA1. This makes it harder to
> make a local source mirror. Would it be possible in the future releases to
> use the SHA1 and have a comment explaining the tag?
You mean this commit from last month?
http://arago-project.org/git/?p=meta-arago.git;a=commitdiff;h=451145b70e1fd922d99ae98041d9801008b6d5bf
--
Denys
next prev parent reply other threads:[~2013-06-14 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 16:54 Updated Core TI-SDK setup and build instructions Denys Dmytriyenko
2013-06-13 18:36 ` Paul Kovitz
2013-06-13 19:06 ` Denys Dmytriyenko
2013-06-14 16:27 ` Paul Kovitz
2013-06-14 16:31 ` Denys Dmytriyenko [this message]
2013-06-14 16:39 ` Paul Kovitz
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=20130614163152.GA7791@edge \
--to=denys@ti.com \
--cc=meta-arago@arago-project.org \
--cc=paul.kovitz@welchallyn.com \
/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.