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
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
