On 15-08-25 01:24 PM, Cristian Bercaru wrote:
Hello!
The Intel Axxia team use git tags in their private github repositories
to mark releases. e.g. 'lsi_axxia_linux_7.8.1.46'
We would like to put tags on commits from the
'standard/(preempt-rt/)axxia/base' branches in linux-yocto-*. Thus, when
pointing our customers to yocto, we could give them the release tag
instead the commit SHA.
Does this interfere with the linux-yocto policy? If not, how can we do
this?
It would cause a problem, since eventually the tree gets full of tags,
and tags that don't have meaning to all the use cases of the tree. Sure,
they are on the BSP branches, but 'git tag' will still list them all.
But what you are describing is exactly what SRCREV_<foo> is for .. you
put a hash into a variable, and the build system ensures that it is
built.
Bruce
Thank you,
Cristian Bercaru
--
_______________________________________________
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
