On 11/4/20 6:29 AM, Robert P. J. Day wrote:
colleague wants to add some perl recipes to a zeus-based image, and
found the meta-cpan layer, which contains a number of desired recipes,
but the structure of that layer seems a bit sparse.
first, here's the entire set of branches:
$ git branch -a
remotes/origin/HEAD -> origin/master
where you can see that the branches jump from thud to master with
nothing in between, so there is no "zeus" branch to focus on. also,
there are absolutely no tags.
finally, it seems that the recipes simply upgrade versions
arbitrarily, all on the master branch, so if you grabbed the "master"
version of any recipe, there's no telling when it might change, which
makes reproducibility a bit iffy.
right, so usually it means maintainers keep master moving forward and perhaps test with latest release or master or perhaps all releases after the thud branch, you have to ask this question to the maintainers. but yes forking and then branching your development from master is perhaps fine.
what is the proper way to take advantage of a layer like this? you
can't even use PREFERRED_VERSION for a given recipe since you can
never predict when that version will suddenly disappear from the
i imagine the best approach is to simply clone the layer, check it
out to a specific commit ID that works for all desired recipes, and
just leave it there. or just individually copy each version of each
recipe one wants into a local layer (yuck).