[OE-core] how to add "uninative binary shim" to local source mirror?

Robert P. J. Day rpjday at crashcourse.ca
Thu Oct 20 09:33:23 UTC 2016


i use a local source mirror to avoid massive fetching; my site.conf:

  SOURCE_MIRROR_URL ?= "file:///home/rpjday/oe/dist/tarballs/"
  INHERIT += "own-mirrors"
  BB_GENERATE_MIRROR_TARBALLS = "1"
  # BB_NO_NETWORK = "1"

and if anything did need to get downloaded, i have a script i run from
inside the downloads/ directory to copy new content into my source
mirror directory (the idea, of course, being to recognize every
possible format of new, fetched content):

  for f in *.gz *.tgz *.bz2 *.xz *.rpm *.zip *.bin ; do
        if [ -f $f -a ! -h $f ] ; then
                echo "Copying $f ..." ; cp $f ~/oe/dist/tarballs/
        fi
  done

i just noticed new fetched content:

NOTE: Fetching uninative binary shim from
http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2;sha256sum=101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca
--2016-10-20 05:22:59--
http://downloads.yoctoproject.org/releases/uninative/1.4/x86_64-nativesdk-libc.tar.bz2

but that fetched content ends up in downloads/ under the subdirectory:

  $ tree uninative/
  uninative/
  └──
  101ff8f2580c193488db9e76f9646fb6ed38b65fb76f403acb0e2178ce7127ca
      ├── x86_64-nativesdk-libc.tar.bz2
      └── x86_64-nativesdk-libc.tar.bz2.done

is it just a matter of copying that bz2 tarball to my local source
mirror? is there some reason that tarball isn't fetched directly into
the downloads/ directory? are there any other "special cases" like
this i should be aware of?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


More information about the Openembedded-core mailing list