linux/meta-openembedded.git/meta-oe/classes/gitpkgv.bbclass, branch master

gitpkgv.bbclass: inspect repository in UNPACKDIR

2025-08-18T14:50:01+00:00

When BB_GIT_SHALLOW = "1" is used, the unpacked gir repository doesn't exist in the download folder, and the class isn't able to inspect the details of the repository. Instead inspect the repository it the UNPACKDIR. Beside this, since BitBake fetcher performs an actual initial shallow clone of the repository when this feature is enabled, it is not possible to determine the exact number of commits. Add a warning about this. Reported-by: WXbet Signed-off-by: Gyorgy Sarvari Signed-off-by: Khem Raj

gitpkgv.bbclass: Fix broken git revison

2025-03-22T16:58:08+00:00

The revision dictionary was built with keys from names list in Bitbake(setup_revisions()). See: https://git.openembedded.org/bitbake/commit/?id=2515fbd10824005fa7f34e87706000c079920366 And used to build names list in gitpkgv.bbclass in the old situation, see: https://git.openembedded.org/meta-openembedded/commit/?id=2920d4909236106e1a36d56b3b20762a308ba3d4 Use name variable to build names list instead of revision variable. Use append() now name variable is a string. Old ipk file name: enigma2_3.13+git3_1_3_0_9_c_7_0_a_4_f_a_6_9_d_6_7_0_1_7_b_b_9_f_7_f_4_d_d_9_d_6_1_0_a_8_c_3_d_20+31309c70a4-r0_dm920.ipk New ipk file name: enigma2_3.13+git21834+31309c70+31309c70a4-r0_dm920.ipk Signed-off-by: Khem Raj

gitpkgver: Update to match bitbake fetcher changes

2025-03-20T16:04:50+00:00

The bitbake fetcher dropped support for multiple revisions on a single url. Update the gitpkgver code to match. Signed-off-by: Richard Purdie Signed-off-by: Khem Raj

gitpkgv.bbclass: adjust the example in comment a bit

2024-02-09T17:52:12+00:00

* the first example isn't very useful anymore since: SRCPV is deferred now from PV to PKGV since: https://git.openembedded.org/openembedded-core/commit/?h=nanbield&id=a8e7b0f932b9ea69b3a218fca18041676c65aba0 * but keep it in the bbclass in case someone is still using it for whatever reason (the version with tag still makes some sense) Signed-off-by: Martin Jansa

gitpkgv: Fix python deprecation warning

2023-05-03T23:26:17+00:00

Fixes DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13 pipes is an alias for shlex therefore switch to using shlex Signed-off-by: Khem Raj

gitpkgv.bbclass: Add support for extending the supported tag formats

2020-01-17T23:44:06+00:00

Introduce GITPKGV_TAG_REGEXP (which defaults to "v(\d.*)") to support dropping other unwanted parts of the found tags than just a leading "v". Any matching groups in the regexp will be concatenated to yield the final version. Signed-off-by: Peter Kjellerstedt Signed-off-by: Khem Raj

gitpkgv.bbclass: Support also lightweight tags

2019-11-20T07:33:03+00:00

When checking for commit specific tags during GITPKGVTAG resolution, use additional '--tags' and '--exact-match' options for 'git describe' command. This changes the behaviour so that in case an annotated tag does not exist for the particular commit, then the latest lightweight (non-annotated) tag is used instead, in case that commit has at least one such tag. Signed-off-by: Niko Mauno Signed-off-by: Khem Raj

gitpkgv.bbclass: Use --git-dir option

2019-11-20T07:33:03+00:00

Avoid redundant shell working directory change by resorting to '--git-dir' option for git command instead. Signed-off-by: Niko Mauno Signed-off-by: Khem Raj

gitpkgv.bbclass: fix versioning with multiple repos

2017-02-22T12:16:48+00:00

gitpkgv class is supposed to use SRCREV_FORMAT variable to define how to smoosh together revision info from multiple repos that are used in a single recipe. It is incorrectly repeating the rev hash for the first repo instead of including the rev from each listed repo. Example: SRC_URI = "git://some-server/purple.git;destsuffix=git/purple;name=purple" SRC_URI += "git://other-server/blue.git;destsuffix=git/blue;name=blue" SRCREV_purple = "${AUTOREV}" SRCREV_blue = "${AUTOREV}" SRCREV_FORMAT = "purple_blue" Suppose gitpkgv calculates "67+ea121ea" for purple repo, and "123+feef001" for blue repo. This should result in a package version with them joined together like so: "67+ea121ea_123+feef001" It didn't. Instead the git hash part for the first repo got repeated: "67+ea121ea_123+ea121ea" Fix this by looking in the right place for the git revisions of 2nd (and following) repos when assembling the full version string. Signed-off-by: S. Lockwood-Childs Signed-off-by: Martin Jansa

remove True option to getVar calls

2016-12-02T08:16:17+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?$( ?[^,()]*), True$ Signed-off-by: Joshua Lock