Home
last modified time | relevance | path

Searched refs:tarballs (Results 1 – 25 of 87) sorted by relevance

1234

/openbmc/linux/scripts/
H A DMakefile.package61 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 Defficiently-fetching-sources.rst9 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 Dstart.rst634 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 Dbluepy_git.bb11 file://0001-bluepy-Fix-username-issue-with-tarballs.patch \
/openbmc/openbmc/poky/meta/conf/distro/include/
H A Dyocto-uninative.inc2 # This include points at uninative tarballs generated and maintained
/openbmc/openbmc/poky/meta/recipes-sato/webkit/
H A Dlibwpe_1.16.0.bb17 # ipstream directory contains tarballs for other components as well.
H A Dwpebackend-fdo_1.14.2.bb23 # ipstream directory contains tarballs for other components as well.
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dvala.bbclass26 # Remove vapigen.m4 that is bundled with tarballs
H A Ddevupstream.bbclass8 # can build both stable tarballs and snapshots from upstream source
H A Dgobject-introspection.bbclass47 # introspection.m4 pre-packaged with upstream tarballs does not yet
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/bluepy/bluepy/
H A D0001-bluepy-Fix-username-issue-with-tarballs.patch4 Subject: [PATCH] bluepy: Fix username issue with tarballs
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/cfengine/
H A Dcfengine-masterfiles_3.21.0.bb23 SRC_URI = "https://cfengine-package-repos.s3.amazonaws.com/tarballs/${BP}.tar.gz \
H A Dcfengine_3.21.0.bb21 SRC_URI = "https://cfengine-package-repos.s3.amazonaws.com/tarballs/${BPN}-community-${PV}.tar.gz \
/openbmc/openbmc/poky/meta/recipes-support/diffoscope/
H A Ddiffoscope_260.bb5 It can compare two tarballs, ISO images, or PDF just as easily."
/openbmc/openbmc/poky/meta/recipes-devtools/perl-cross/
H A Dperlcross_1.5.2.bb8 # but is not provided inside the release tarballs
/openbmc/openbmc/poky/meta/recipes-devtools/dpkg/dpkg/
H A D0007-dpkg-deb-build.c-Remove-usage-of-clamp-mtime-in-tar.patch10 build tarballs [1].
/openbmc/openbmc/poky/meta/recipes-core/kbd/kbd/
H A D0001-Remove-non-free-Agafari-fonts.patch29 tarballs before putting it to their servers.
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-click-spinner/
H A D0001-Update-Versioneer-to-0.22.patch36 -# 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 Dsparse.rst78 You can get tarballs of the latest released versions from:
/openbmc/openbmc/poky/meta/recipes-core/images/
H A Dbuild-appliance-image_15.0.0.bb56 # Remove the git2_* tarballs -- this is ok since we still have the git2/.
/openbmc/openbmc/poky/documentation/migration-guides/
H A Dmigration-3.0.rst225 - Github archive tarballs --- these are not guaranteed to be stable.
226 Consequently, it is likely that the tarballs will be refreshed and
H A Drelease-notes-4.2.1.rst29 - dhcpcd: use git instead of tarballs
H A Drelease-notes-4.0.11.rst35 - dhcpcd: use git instead of tarballs
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/
H A Dbitbake-user-manual-ref-variables.rst297 Causes tarballs of the Git repositories, including the Git metadata,
301 For performance reasons, creating and placing tarballs of the Git
308 "1" causes bitbake to generate shallow mirror tarballs when fetching git
310 tarballs is controlled by :term:`BB_GIT_SHALLOW_DEPTH`.
313 enabled, bitbake will generate shallow mirror tarballs by default for git
322 …generating mirror tarballs of `shallow git repositories <https://riptutorial.com/git/example/4584/…
352 the number of commits to include in generated shallow mirror tarballs.
358 generating shallow mirror tarballs.
1016 everything except Git repositories. If you want tarballs of Git
1536 specified subdirectory. This option is useful for unusual tarballs
/openbmc/openbmc/poky/bitbake/lib/bb/fetch2/
H A D__init__.py987 def adduri(ud, uris, uds, mirrors, tarballs): argument
994 for tarball in tarballs:
1019 adduri(newud, uris, uds, localmirrors, tarballs)
1026 adduri(newud, uris, uds, localmirrors, tarballs)

1234