/openbmc/linux/scripts/ |
H A D | Makefile.package | 61 linux-tarballs := $(addprefix linux, .tar.gz .tar.bz2 .tar.lzma .tar.xz) 63 targets += $(linux-tarballs) 64 $(linux-tarballs): archive-args = --prefix=linux/ $$(cat $<) 65 $(linux-tarballs): .tmp_HEAD FORCE 185 dir-tarballs := $(addprefix linux-$(KERNELRELEASE)-$(ARCH), .tar .tar.gz .tar.bz2 .tar.xz .tar.zst) 187 $(dir-tarballs): tar-install 224 perf-tarballs := $(addprefix perf-$(KERNELVERSION), .tar .tar.gz .tar.bz2 .tar.xz .tar.zst) 226 targets += $(perf-tarballs) 227 $(perf-tarballs): archive-args = --prefix=perf-$(KERNELVERSION)/ $(perf-archive-args) 228 $(perf-tarballs): tools/perf/MANIFEST .tmp_perf/HEAD .tmp_perf/PERF-VERSION-FILE FORCE
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | efficiently-fetching-sources.rst | 9 locating and downloading all the source tarballs. For images, 21 all of the source tarballs. Maybe you have been working with another 23 sizable directory of source tarballs. Or, perhaps someone else has such 26 checks local directories first for existing tarballs before checking the 38 variable causes the OpenEmbedded build system to generate tarballs of 41 performance reasons, generating and storing these tarballs is not the
|
H A D | start.rst | 634 from which you can locate and download tarballs of any Yocto Project 636 tarballs similar to the tarballs located in the Index of Releases 648 will lead to the download tarballs for the release. 658 #. *Download Tools or Board Support Packages (BSPs):* Next to the tarballs you
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/bluepy/ |
H A D | bluepy_git.bb | 11 file://0001-bluepy-Fix-username-issue-with-tarballs.patch \
|
/openbmc/openbmc/poky/meta/conf/distro/include/ |
H A D | yocto-uninative.inc | 2 # This include points at uninative tarballs generated and maintained
|
/openbmc/openbmc/poky/meta/recipes-sato/webkit/ |
H A D | libwpe_1.16.0.bb | 17 # ipstream directory contains tarballs for other components as well.
|
H A D | wpebackend-fdo_1.14.3.bb | 23 # ipstream directory contains tarballs for other components as well.
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | vala.bbclass | 26 # Remove vapigen.m4 that is bundled with tarballs
|
H A D | devupstream.bbclass | 8 # can build both stable tarballs and snapshots from upstream source
|
H A D | gobject-introspection.bbclass | 47 # introspection.m4 pre-packaged with upstream tarballs does not yet
|
/openbmc/openbmc/poky/meta/classes-global/ |
H A D | retain.bbclass | 47 # * The tarballs have the tarball name as a top-level directory so that 48 # multiple tarballs can be extracted side-by-side easily. 75 # multiple tarballs can be extracted side-by-side
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/bluepy/bluepy/ |
H A D | 0001-bluepy-Fix-username-issue-with-tarballs.patch | 4 Subject: [PATCH] bluepy: Fix username issue with tarballs
|
/openbmc/openbmc/poky/meta/recipes-support/diffoscope/ |
H A D | diffoscope_284.bb | 5 It can compare two tarballs, ISO images, or PDF just as easily."
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/cfengine/ |
H A D | cfengine-masterfiles_3.21.5.bb | 23 SRC_URI = "https://cfengine-package-repos.s3.amazonaws.com/tarballs/${BP}.tar.gz \
|
H A D | cfengine_3.21.0.bb | 21 SRC_URI = "https://cfengine-package-repos.s3.amazonaws.com/tarballs/${BPN}-community-${PV}.tar.gz \
|
/openbmc/openbmc/poky/meta/recipes-devtools/perl-cross/ |
H A D | perlcross_1.6.bb | 8 # but is not provided inside the release tarballs
|
/openbmc/openbmc/poky/meta/recipes-devtools/dpkg/dpkg/ |
H A D | 0007-dpkg-deb-build.c-Remove-usage-of-clamp-mtime-in-tar.patch | 10 build tarballs [1].
|
/openbmc/openbmc/poky/meta/recipes-extended/man-db/files/ |
H A D | flex.patch | 9 tarballs include the code.
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-click-spinner/ |
H A D | 0001-Update-Versioneer-to-0.22.patch | 36 -# unpacked source archive. Distribution tarballs contain a pre-generated copy 40 +# feature). Distribution tarballs (built by setup.py sdist) and build 155 + Source tarballs conventionally unpack into a directory that includes both 741 @@ -27,9 +23,10 @@ system, and maybe making new tarballs. 783 - keywords in generated tarballs. The 'build' and 'sdist' commands will 852 - generated `_version.py` in sdist tarballs 871 -current version string. All generated tarballs should include an embedded 881 -tarballs with `git archive`), the process is: 942 + distributions (and upload multiple independently-installable tarballs). 1226 # feature). Distribution tarballs (built by setup.py sdist) and build [all …]
|
/openbmc/linux/Documentation/dev-tools/ |
H A D | sparse.rst | 78 You can get tarballs of the latest released versions from:
|
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
H A D | bitbake-user-manual-ref-variables.rst | 285 Causes tarballs of the Git repositories, including the Git metadata, 289 For performance reasons, creating and placing tarballs of the Git 296 "1" causes bitbake to generate shallow mirror tarballs when fetching git 298 tarballs is controlled by :term:`BB_GIT_SHALLOW_DEPTH`. 301 enabled, bitbake will generate shallow mirror tarballs by default for git 310 …generating mirror tarballs of `shallow git repositories <https://riptutorial.com/git/example/4584/… 340 the number of commits to include in generated shallow mirror tarballs. 346 generating shallow mirror tarballs. 1008 everything except Git repositories. If you want tarballs of Git 1528 specified subdirectory. This option is useful for unusual tarballs
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | migration-3.0.rst | 225 - Github archive tarballs --- these are not guaranteed to be stable. 226 Consequently, it is likely that the tarballs will be refreshed and
|
H A D | release-notes-4.0.11.rst | 35 - dhcpcd: use git instead of tarballs
|
/openbmc/openbmc/poky/meta/recipes-core/images/ |
H A D | build-appliance-image_15.0.0.bb | 56 # Remove the git2_* tarballs -- this is ok since we still have the git2/.
|
/openbmc/openbmc/poky/bitbake/lib/bb/fetch2/ |
H A D | __init__.py | 995 def adduri(ud, uris, uds, mirrors, tarballs): argument 1002 for tarball in tarballs: 1027 adduri(newud, uris, uds, localmirrors, tarballs) 1034 adduri(newud, uris, uds, localmirrors, tarballs)
|