debian-rcm - Debian packaging for rcm

	Commit message (Collapse)	Author	Age
*	Prepare for the next release	Mike Burns	2014-05-14
\| \| \| \| \|	The Debian changelog and NEWS.md.in need to be updated to prepare for the auto-generation next time.
*	Post-release cleanup	Mike Burns	2014-03-28
\|
*	Fresh changelogs, ready for a new commit	Mike Burns	2014-03-07
\|
*	Start bringing in the Makefile.am from gitsh	Mike Burns	2014-02-26
\| \| \| \| \| \| \| \| \| \| \|	It introduces the `Makefile.am` from gitsh, and abstracts it a bit. This `Makefile.am`, or most of it, could be dropped into gitsh again. How to use it is documented in `DEVELOPERS.md`. The whole release process is more consistent and simple: `make release` to build a tarball, Homebrew, Arch, Debian, HTML (from manpages), and tag it, pushed to the various repos, and with cleanup. The `release` target is composed of smaller targets that stack well.
*	Add a release target	Mike Burns	2013-08-01
\| \| \| \| \| \| \| \| \| \| \| \| \|	The `make release` command will build the Debian package, push the version to a git tag on GitHub, and upload the docs to GitHub pages. This also adds a `deb` target, along with `build-docs`, `upload-docs`, `build-tag`, and `push-tag`. In addition, introduce a `NEWS.md` file. Both `rcm.sh.in` and `NEWS.md.in` will act as input files. This is to abstract over the version number.
*	Able to generate deb packages	Mike Burns	2013-07-27
	The following command can generate a Debian package: debuild -us uc The directory structure and tarball must be perfectly set up first. This is documented in `DEVELOPERS.md`.