debian-rcm - Debian packaging for rcm

	Commit message (Collapse)	Author	Age
*	Release for unstableHEAD 1.3.4-1 master	Benjamin Barenblat	2020-10-15
\|
*	Update compat level and Standards-Version	Benjamin Barenblat	2020-10-15
\|
*	Refresh patches	Benjamin Barenblat	2020-10-15
\|
*	Start packaging 1.3.4-1	Benjamin Barenblat	2020-10-15
\|
*	Release for unstable1.3.3-3	Benjamin Barenblat	2019-10-27
\|
*	Update Standards-Version to 4.4.1	Benjamin Barenblat	2019-10-27
\| \| \| \|	No changes were required.
*	Use Python 3 for tests	Benjamin Barenblat	2019-10-27
\|
*	Set Multi-Arch: foreign1.3.3-2	Benjamin Barenblat	2019-01-03
\|
*	Release for unstable1.3.3-1	Benjamin Barenblat	2018-12-20
\|
*	Use sh as the shell for rcm	Benjamin Barenblat	2018-12-20
\| \| \| \| \| \|	rcm only requires a POSIX-compliant shell – not Bash. The various sh options in Debian are POSIX-compliant, and many of them are substantially faster than Bash. Force rcm to run under /bin/sh.
*	Patch out references to macOS in the man pages	Benjamin Barenblat	2018-12-20
\| \| \| \| \|	Debian isn’t macOS; our man pages don’t need to cover hostname(1)’s foibles there.
*	Move contributor list to its own file	Benjamin Barenblat	2018-12-20
\| \| \| \| \| \| \| \| \| \| \| \|	Upstream puts the output of git-shortlog into a man page. However, that’s not suitable for Debian – we can’t ship the entire Git history in a source package. It’s also unclear whether contributor lists even really belong in a man page. Pregenerate the contributor list, and install it in /usr/share/doc/rcm. Future developers: You can regenerate the contributor list with git shortlog -es v$UPSTREAM_VERSION >debian/doc/CONTRIBUTORS
*	Begin packaging 1.3.3	Benjamin Barenblat	2018-12-20
\|
*	Remove upstream’s Debian packaging	Benjamin Barenblat	2018-12-20
\|
*	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`.