based on my recommendation, colleague created a local source mirror
to start collecting tarballs so as to minimize amount of downloading
for various builds. names of tarballs that correspond to fixed
(versioned) tarballs was fairly obvious, but he got stuck trying to
local source mirror a tarball for googletest (from meta-oe), which
contains (among other things):
googletest_git.bb
...
PV = "1.10.0"
S = "${WORKDIR}/git"
SRCREV = "703bd9caab50b139428cea1aaff9974ebee5742e"
SRC_URI = "git://github.com/google/googletest.git"
he wasn't sure what name the tarball should have in order to be
recognized in the local source mirror. i didn't have the answer off
the top of my head, but since for years i've enhanced all my builds
with a site.conf file containing:
SOURCE_MIRROR_URL ?= "file:///home/rpjday/oe/dist/tarballs/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
i just added googletest to a random build to see what i'd get, and
got:
git2_github.com.google.googletest.git.tar.gz
i guess i'd never paid close attention to the name generation for such
things, but i'm *assuming* that the name generation by the appropriate
fetcher code simply encodes everything there is to know about the
source so that the appropriate tarball is recognized as the local
source mirror version for that recipe. is that about right?
second question: clearly, the simple name of that tarball doesn't
encode the PV or SRCREV values, so what happens if the base recipe
suddenly bumps PV up to 1.11.0? i'm sure the answer is obvious, i've
just never thought about it.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#150743):
https://lists.openembedded.org/g/openembedded-core/message/150743
Mute This Topic: https://lists.openembedded.org/mt/82257890/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
