pax_global_header00006660000000000000000000000064141360363650014521gustar00rootroot0000000000000052 comment=daa017464e266380cdeb4e6f9613eba9182b59a3 dbus-5.0.6/000077500000000000000000000000001413603636500124665ustar00rootroot00000000000000dbus-5.0.6/.github/000077500000000000000000000000001413603636500140265ustar00rootroot00000000000000dbus-5.0.6/.github/workflows/000077500000000000000000000000001413603636500160635ustar00rootroot00000000000000dbus-5.0.6/.github/workflows/go.yml000066400000000000000000000013561413603636500172200ustar00rootroot00000000000000name: Go on: push: branches: [ master ] pull_request: branches: [ master ] jobs: build: name: Build runs-on: ubuntu-latest steps: - name: Set up Go 1.x uses: actions/setup-go@v2 with: go-version: ^1.13 - name: Check out code into the Go module directory uses: actions/checkout@v2 - name: Install dbus run: sudo apt-get install dbus dbus-x11 - name: Get dependencies run: | go get -v -t -d ./... if [ -f Gopkg.toml ]; then curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh dep ensure fi - name: Build run: go build -v ./... - name: Test run: go test -v ./... dbus-5.0.6/CONTRIBUTING.md000066400000000000000000000027141413603636500147230ustar00rootroot00000000000000# How to Contribute ## Getting Started - Fork the repository on GitHub - Read the [README](README.markdown) for build and test instructions - Play with the project, submit bugs, submit patches! ## Contribution Flow This is a rough outline of what a contributor's workflow looks like: - Create a topic branch from where you want to base your work (usually master). - Make commits of logical units. - Make sure your commit messages are in the proper format (see below). - Push your changes to a topic branch in your fork of the repository. - Make sure the tests pass, and add any new tests as appropriate. - Submit a pull request to the original repository. Thanks for your contributions! ### Format of the Commit Message We follow a rough convention for commit messages that is designed to answer two questions: what changed and why. The subject line should feature the what and the body of the commit should describe the why. ``` scripts: add the test-cluster command this uses tmux to setup a test cluster that you can easily kill and start for debugging. Fixes #38 ``` The format can be described more formally as follows: ``` :