Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Bump to 1.3.1, prepare for release | Mike Burns and Eric Collins | 2016-12-26 |
| | | | | | - Use SHA256 in Arch and Homebrew packages. - Use OpenSSL to calculate the SHA256 sum, for portability. | ||
* | PKGBUILD-git improvements | Michael Reed | 2014-07-09 |
| | | | | | | | | | - Remove two configure flags which just caused warnings. - Replace `pkgver` function with a working one. - Explicititly `cd` into `srcdir` before `gitname` as found in `PKGBUILD-git.proto`. - Bump `pkgrel`. - Specify correct package version. | ||
* | Add -git PKGBUILD | patrick brisbin | 2014-05-23 |
| | | | | This allows people to install rcm-git on Arch. | ||
* | 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 Arch PKGBUILD | patrick brisbin | 2013-08-01 |
https://aur.archlinux.org/packages/rcm-git/ |