pax_global_header00006660000000000000000000000064142066631130014514gustar00rootroot0000000000000052 comment=e523abc905595cf17fb0001a7d77eaaddfaa216d dbus-5.1.0/000077500000000000000000000000001420666311300124545ustar00rootroot00000000000000dbus-5.1.0/.github/000077500000000000000000000000001420666311300140145ustar00rootroot00000000000000dbus-5.1.0/.github/workflows/000077500000000000000000000000001420666311300160515ustar00rootroot00000000000000dbus-5.1.0/.github/workflows/test.yml000066400000000000000000000017651420666311300175640ustar00rootroot00000000000000name: Test on: push: branches: [ master ] pull_request: branches: [ master ] jobs: test: runs-on: ubuntu-latest strategy: fail-fast: false matrix: go-version: [1.16.x, 1.17.x, 1.18.0-beta1] race: ["-race", ""] steps: - name: Set up Go uses: actions/setup-go@v2 with: stable: '!contains(${{ matrix.go-version }}, "beta") && !contains(${{ matrix.go-version }}, "rc")' go-version: ${{ matrix.go-version }} - name: Checkout uses: actions/checkout@v2 - name: Install dbus run: sudo apt-get install dbus dbus-x11 - name: Build run: go build ${{ matrix.race }} -v ./... - name: Test run: go test ${{ matrix.race }} -v ./... codespell: runs-on: ubuntu-20.04 steps: - uses: actions/checkout@v2 - name: install deps # Version of codespell bundled with Ubuntu is way old, so use pip. run: pip install codespell - name: run codespell run: codespell dbus-5.1.0/CONTRIBUTING.md000066400000000000000000000027141420666311300147110ustar00rootroot00000000000000# 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: ``` :