evocheck/README.md

71 lines
1.5 KiB
Markdown
Raw Normal View History

# Evocheck
This program scans the machine it is run on and verifies if it
adheres to the Evolix standard, non-compliance warnings are outputted
on standard out.
It is currently adapted for Debian and OpenBSD systems.
Configure by modifying evocheck.cf and use the VagrantFile to test
it.
## How to build the package for a new Debian release
On the master branch, add the last stable version with a release tag.
```
git tag -s v<VERSION> -m 'New release'
git push --tags
```
Checkout the branch debian, merge the master branch.
2009-07-18 20:27:22 +02:00
2017-12-14 11:29:07 +01:00
```
git checkout debian
git merge master --no-ff
dch -v <VERSION>-1
gbp buildpackage --git-debian-branch=debian --git-upstream-tree=master --git-export-dir=/tmp/build-area --git-ignore-new
2017-12-14 11:29:07 +01:00
```
2009-07-18 20:27:22 +02:00
If the build is OK, you can now build the final package.
2009-07-18 20:27:22 +02:00
2017-12-14 11:29:07 +01:00
```
dch -D stretch -r
gbp buildpackage --git-debian-branch=debian --git-upstream-tree=master --git-export-dir=/tmp/build-area --git-tag --git-sign --git-keyid=<KEY>
```
## Testing
Evocheck can be tested with Vagrant, if you don't have installed it yet :
~~~
apt install vagrant vagrant-libvirt
~~~
You can now start your Vagrant machine and connect to it :
~~~
vagrant up
vagrant ssh
sudo -i
~~~
Evocheck can be run with :
~~~
/usr/share/scripts/evocheck.sh
~~~
### Deployment
Launch **vagrant rsync-auto** in a terminal to automatically synchronise
your local code with the Vagrant VM :
~~~
vagrant rsync-auto
~~~
## License
This is an [Evolix](https://evolix.com) project and is licensed
under the GPLv3, see the [LICENSE](LICENSE) file for details.