pax_global_header00006660000000000000000000000064127600167500014516gustar00rootroot0000000000000052 comment=43e4800a6165b4e02bb2a36673c54b230d6f7b26 go-systemd-12/000077500000000000000000000000001276001675000133755ustar00rootroot00000000000000go-systemd-12/.travis.yml000066400000000000000000000015721276001675000155130ustar00rootroot00000000000000sudo: required services: - docker env: global: - GOPATH=/opt - BUILD_DIR=/opt/src/github.com/coreos/go-systemd matrix: - DOCKER_BASE=ubuntu:16.04 - DOCKER_BASE=debian:stretch before_install: - docker pull ${DOCKER_BASE} - docker run --privileged -e GOPATH=${GOPATH} --cidfile=/tmp/cidfile ${DOCKER_BASE} /bin/bash -c "apt-get update && apt-get install -y build-essential git golang dbus libsystemd-dev libpam-systemd && go get github.com/coreos/pkg/dlopen && go get github.com/godbus/dbus" - docker commit `cat /tmp/cidfile` go-systemd/container-tests - rm -f /tmp/cidfile install: - docker run -d --cidfile=/tmp/cidfile --privileged -e GOPATH=${GOPATH} -v ${PWD}:${BUILD_DIR} go-systemd/container-tests /bin/systemd --system script: - docker exec `cat /tmp/cidfile` /bin/bash -c "cd ${BUILD_DIR} && ./test" after_script: - docker kill `cat /tmp/cidfile` go-systemd-12/CONTRIBUTING.md000066400000000000000000000051541276001675000156330ustar00rootroot00000000000000# How to Contribute CoreOS projects are [Apache 2.0 licensed](LICENSE) and accept contributions via GitHub pull requests. This document outlines some of the conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contribution accepted. # Certificate of Origin By contributing to this project you agree to the Developer Certificate of Origin (DCO). This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution. See the [DCO](DCO) file for details. # Email and Chat The project currently uses the general CoreOS email list and IRC channel: - Email: [coreos-dev](https://groups.google.com/forum/#!forum/coreos-dev) - IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org Please avoid emailing maintainers found in the MAINTAINERS file directly. They are very busy and read the mailing lists. ## Getting Started - Fork the repository on GitHub - Read the [README](README.md) 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! ### Coding Style CoreOS projects written in Go follow a set of style guidelines that we've documented [here](https://github.com/coreos/docs/tree/master/golang). Please follow them when working on 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: ``` :