linux/meta-virtualization.git/recipes-devtools/go/go-fsnotify_git.bb, branch container-cross-install

devtools: adapt to UNPACKDIR changes

2025-06-26T02:55:55+00:00

This commit updates the container recipes to the OE core UNPACKDIR changes. - We drop references to WORKDIR - We adjust destsuffix fetches to use BB_GIT_DEFAULT_DESTSUFFIX instead of 'git' - Update our GOPATH references to use UNPACKDIR - Drop S = assignemnts where possible Signed-off-by: Bruce Ashfield

devtools: depreciate the go source-only packages

2024-03-15T17:17:19+00:00

We are now using vendoring from the upstream repos, or creating our own vendor directory. We no longer need these source only recipes. Add an inherit to each recipe to warn that it will be removed in the future. Signed-off-by: Bruce Ashfield

recipes/classes/scripts: Drop SRCPV usage

2023-08-24T01:38:21+00:00

bitbake has been enhanced such that SRCPV is no longer needed in PV to handle updating git hashes and task signatures. We can simplify our PV by dropping SRCPV Signed-off-by: Bruce Ashfield

go-fsnotify: update to v1.5.1

2022-01-14T18:31:32+00:00

Bumping fsnotify to version v1.5.1-7-gaf855d7 We update the license checksum, due to new copyright dates, and include the following commits: af855d7 Final Notice: Maintainers Wanted 62a598a maintainers wanted d696f5c revise contributing 6e1d4e4 update readme 83f9fe6 Test on Go 1.18 and two most recent versions (#411) 0aba082 Update issue templates (#410) 3eb7fa4 Removed dead link 466b39d prepare 1.5.1, retract 1.5.0 b98ede5 Revert "Add AddRaw to not follow symlinks + Fix link folloing on Windows (#289)" dfdb645 revise pull request template 08848a0 v1.5.0 preparation (#380) e2e9517 Add AddRaw to not follow symlinks + Fix link folloing on Windows (#289) 82ee6f3 Update test matrix for go 1.17 stable release (#385) 16f0d42 add //go:build lines + add 1.17.0-rc2 to test matrix (#377) cc8365b Update x/sys to latest (#379) 2fb15b1 Drop support/testing for Go 1.11 and earlier (#381) 5ce1ba4 Remove Travis CI and references ed6d2f5 Add lint+vet+old versions to GitHub Action 42e9219 introduce GitHub Actions 7f4cf4d Fix unsafe pointer conversion (#325) 45d7d09 Move example usage to the readme 4bf2d1f Updating the FAQ section for supportability with NFS & FUSE filesystems. dc27d96 drop 1.8.x from Travis CI fce5a44 2019 ecf2c4d revise editor config 0a05407 Add Go modules ab058b4 readme: plan to support fanotify 924410f Open files with CLOEXEC 1485a34 Also create epoll and pipe fds with close-on-exec (#155) (#219) 11844c0 readme: remove AppVeyor badge 85de84f Add windows to travis matrix 2216558 Fix lint issue with error doc string 9152fb1 only run golint on latest version of go ccc981b Check if channels are closed in the example (#244) 1f285c6 darwin tests: Exchangedata is deprecated on 10.13 7b866c9 travis: less verbose tests 8ba2b19 [#234] t.Fatalf -> t.Errorf in go routines (#266) 70cc4a1 Fix TestInotifyOverflow (#265) 1d13583 TravisCI: updating test versions c282820 v1.4.7 a6f391c travis: test on Go 1.9.x ea33dcb Fix missing verb on format string (#228) 3d33f50 Fix possible deadlock on closing the watcher on kqueue (#230) 4da3e2c Fix deadlock in Remove (linux/inotify) ff7bc41 Watch.Add improvements (avoid race, fix consistency, reduce garbage) (#189) 7d7316e travis: update for Go 1.8 a904159 Moved FAQ into the README fd9ec7d Properly handle inotify's IN_Q_OVERFLOW event (#149) bd2828f replace references to OS X with macOS 629574c v1.4.2 abf5e85 pull request and issue template (#179) 11054bc Create inotify fd with close-on-exec (#178) 944cff2 v1.4.1 5c1390e deflake inotify stress test (#177) b4f2a68 rm go1.5.4 from travis config since the linter doesn't build in 1.5 (#175) c07fd86 readme: remove gocover.io badge b3baf18 update link to contributing to external git repos 26b17cd v1.4.0 c3181d8 add @oozie to AUTHORS 55579be Add a String() func to Event.Op (#165) f12c623 Bump Travis to Go 1.6.3 (#156) a8a77c9 v1.3.1 51d3cc5 Use filepath.Join() (#153) 30411db global: switch to x/sys/unix 836bfd9 Update Travis config to Go 1.5.4 and 1.6.1 Signed-off-by: Bruce Ashfield

go-fsnotify: switch to main branch

2022-01-14T18:31:32+00:00

The upstream project has changed from master -> main, so we update our branch to match .. otherwise, we fail the fetch! Signed-off-by: Bruce Ashfield

global: convert github SRC_URIs to use https protocol

2021-11-03T13:37:00+00:00

* apply the same also for recipes using PKG_NAME starting with github.com which the conversion script doesn't update automatically Signed-off-by: Martin Jansa Signed-off-by: Bruce Ashfield

global: add explicit branch to all SRC_URIs

2021-11-02T13:57:03+00:00

As introduced in the oe-core post: https://lists.openembedded.org/g/openembedded-core/message/157623 SRC_URIs without an explicit branch will generate warnings, and eventually be an error. We run the provided conversion script to make sure that meta-virt is ready for the change. Signed-off-by: Bruce Ashfield

global: overrides syntax conversion

2021-08-02T21:17:53+00:00

OEcore/bitbake are moving to use the clearer ":" as an overrides separator. This is pass one of updating the meta-virt recipes to use that syntax. This has only been minimally build/runtime tested, more changes will be required for missed overrides, or incorrect conversions Note: A recent bitbake is required: commit 75fad23fc06c008a03414a1fc288a8614c6af9ca Author: Richard Purdie Date: Sun Jul 18 12:59:15 2021 +0100 bitbake: data_smart/parse: Allow ':' characters in variable/function names It is becomming increasingly clear we need to find a way to show what is/is not an override in our syntax. We need to do this in a way which is clear to users, readable and in a way we can transition to. The most effective way I've found to this is to use the ":" charater to directly replace "_" where an override is being specified. This includes "append", "prepend" and "remove" which are effectively special override directives. This patch simply adds the character to the parser so bitbake accepts the value but maps it back to "_" internally so there is no behaviour change. This change is simple enough it could potentially be backported to older version of bitbake meaning layers using the new syntax/markup could work with older releases. Even if other no other changes are accepted at this time and we don't backport, it does set us on a path where at some point in future we could require a more explict syntax. I've tested this patch by converting oe-core/meta-yocto to the new syntax for overrides (9000+ changes) and then seeing that builds continue to work with this patch. (Bitbake rev: 0dbbb4547cb2570d2ce607e9a53459df3c0ac284) Signed-off-by: Richard Purdie Signed-off-by: Bruce Ashfield

Use SRCPV instead of SRCREV where possible

2019-01-16T15:28:26+00:00

This change reduces the length of ${PV} for several recipes and gives us auto-incrementing version numbers. Signed-off-by: Paul Barker Signed-off-by: Bruce Ashfield

go-fsnotify: switch to new repository on github

2018-03-22T04:48:09+00:00

fsnotify is changed to new repository on gihub, so adapt this chanage accordingly to avoid fetch failure. Signed-off-by: Yunguo Wei Signed-off-by: Bruce Ashfield