summaryrefslogtreecommitdiff
path: root/README.md
Commit message (Collapse)AuthorAge
* add Void Linux install instructionsGravatar maxice82018-07-06
|
* Remove redundant \Gravatar Yota Toyama2017-11-02
|
* Update README.mdGravatar Alan Yee2017-10-27
| | | | Replace OS X with macOS
* add Gentoo install instructionsGravatar Florian Tham2017-06-07
|
* Update thoughtbot logoGravatar Tyson Gach2017-03-10
|
* Update location of thoughtbot's PGP keyGravatar Matthew Horan2017-02-01
|
* Fedora 22 to 25 is supported.Gravatar Mike Burns2017-01-07
|
* Document the official thoughtbot Debian repositoryGravatar Eric Collins2017-01-07
| | | | Big ups to Eric Collins for leading this charge.
* Fix the SHA for the tarballGravatar Mike Burns2017-01-07
| | | | I need to automate this.
* Bump to 1.3.1v1.3.1Gravatar Mike Burns2017-01-07
|
* Add installation instructions for KororaGravatar Ben Stephens2016-04-08
| | | | | | | | | Korora can make use of Fedora packages by specifying the version and architecture explictly. Rephrased by Mike Burns for consistency. Closes #176.
* Fix SHA256 for tarballGravatar Rafael Santos2016-02-02
|
* Add MacPorts installation instructionsGravatar Casey Rodarmor2016-01-21
|
* We have a FreeBSD packageGravatar Mike Burns2015-12-14
| | | | | | | | I just learned, when I upgraded a server that I share with mhoran, that there is a FreeBSD package. And he didn't tell me! Thanks to Leonardo for maintaining it and to mhoran for quietly indicating that it exists.
* Fix SHA for Debian packageGravatar Mike Burns2015-11-06
|
* Remove Ubuntu distro specificationGravatar Martin Frost2015-11-04
| | | | | Since there are now packages available for newer Ubuntu dsitributions than the ones specified in README.md, just remove the parentheses.
* Drop Gentoo instructionsGravatar Mike Burns2015-11-01
| | | | | | | | Anton has stopped maintaining the rcm package for Gentoo, so remove mention of them. Thank you, Anton, for the work you had done, and best of luck to you in the future!
* Update AUR link in READMEGravatar Blake Williams2015-11-01
| | | | | The old package was removed during the AUR migration to a git based platform and now has a new maintainer and package url.
* Add Fedora installation instructions to READMEGravatar Carl van Tonder2015-11-01
| | | | | | References the `seeitcoming/rcm` COPR. Closes #156.
* Note the requirement for root privs to installGravatar Devraj Mehta2015-09-04
| | | | | | | | When installing using the default arguments to `configure`, root privileges are required. Use a "sudo" prefix to notate this. NB. root privileges are not needed when installing to a prefix under your control.
* Add SHAs for our downloadsGravatar Mike Burns2015-06-05
| | | | Add a SHA256 hash for the Debian and tarball downloads. Closes #127.
* Add "About thoughtbot" section to READMEGravatar Joe Ferris2015-03-09
|
* Install from OpenBSD packagesGravatar Mike Burns2014-11-16
| | | | | | | | We are now in the OpenBSD ports tree, so add pkg_add(1) instructions. This only works on -current right now. While here, re-arrange installation instructions to be alphabetical by OS (or distribution) name.
* Spell add-apt-repository in Ubuntu instructionsGravatar David Alexander2014-11-07
|
* Installation instructions for UbuntuGravatar Martin Frost2014-08-01
| | | | | | Add instructions for how to install rcm on Ubuntu using the [~martin-frost/thoughtbot-rcm PPA](https://launchpad.net/~martin-frost/+archive/ubuntu/thoughtbot-rcm)
* Link to the Web manpagesGravatar Mike Burns2014-06-04
| | | | | To give people a preview of the joy they will expect to find when they start using rcm, link to the HTML manpages from the README.
* Release 1.2.3v1.2.3Gravatar Mike Burns2014-05-09
|
* Update the copyright, assign it to thoughtbotGravatar Mike Burns2014-05-05
| | | | This is a thoughtbot project now, so assign copyright to thoughtbot.
* Link to the openSUSE (and RHEL and CentOS) packageGravatar Andrei Dziahel2014-04-25
| | | | | This project is now a part of openSUSE, which can provide easy-to-use packages for RHEL and CentOS. Link to that.
* An integration test suiteGravatar patrick brisbin2014-04-08
| | | | | | | | | | | | | | | | | | | | | | | This test suite uses cram to run integration tests through `/bin/sh`. The tests are all high-level acceptance tests; they should work regardless of the implemention code. To run them, you must first install cram: sudo pip install cram Then the `check` target will run them: make check Failure output should be printed clearly to stdout, but in general: full test output is in `test/test-suite.log` and output specific to a test named `foo.t` is in `foo.t.log`. Tests are now encouraged in `CONTRIBUTING.md` as part of the normal pull request process. This is a TAP-enabled test suite.
* Post-release cleanupGravatar Mike Burns2014-03-28
|
* Fix spelling of CONTRIBUTING.md in READMEGravatar John Axel Eriksson2014-03-10
|
* Last-minute changesv1.2.1Gravatar Mike Burns2014-03-07
| | | | | * Debian package has a -2 in its filename. Of course. * Build HTML docs in the top-level gh-pages directory.
* Update installation instructions for 1.2.1Gravatar Mike Burns2014-03-07
| | | | | This also ties up any loose ends, including where to find the tarball and how to contribute.
* Add install instruction on Gentoo-based systemsGravatar Anton Ilin2014-02-24
| | | | | | Add instruction how to install rcm on a Gentoo-based GNU/Linux distribution. Currently the overlay is maintained by Anton Ilin (bronislav).
* Bump to 1.2.0.v1.2.0Gravatar Mike Burns2014-02-03
|
* Rename the homebrew repo.Gravatar George Brocklehurst2014-01-31
| | | | Having a single homebrew tap for all of thoughtbot's projects makes sense.
* Mention rcdnGravatar Mike Burns2013-12-09
|
* Reference the thoughtbot URLsGravatar Mike Burns2013-12-09
| | | | | Now that Mike (that's me) transfered this project to thoughtbot, move all the URLs to thoughtbot-specific ones, too.
* Bump to 1.1.0v1.1.0Gravatar Mike Burns2013-09-12
|
* Some 1.0.0 cruftGravatar Mike Burns2013-08-03
| | | | I'll figure out `make release` someday.
* Document Debian installation instructionsGravatar Mike Burns2013-08-01
| | | | | Currently the deb file is hosted on my personal server. Download it then use `dpkg` to install it.
* Document the Arch installationGravatar Mike Burns2013-08-01
| | | | | SInce Arch users choose from different installation options for themselves, just link to the AUR page and let them decide.
* Homebrew installationGravatar Mike Burns2013-08-01
| | | | | | | This can be installed using Homebrew for OS X. brew tap mike-burns/rcm brew install rcm
* Re-write using GNU autoconf and automakeGravatar Mike Burns2013-07-27
| | | | Replace the `Makefile` with a `configure.ac` and a set of `Makefile.am`.
* Add lsrcGravatar Mike Burns2013-07-12
| | | | | | | | | The `lsrc` command works just like the `rcup` command but instead of making symlinks and directories, it just lists all the files that would be symlinks. It prints the destination (e.g. `~/.foo`) and the source (`~/.dotfiles/foo`), separated by a colon. Re-write `rcup` in terms of `lsrc`.
* Support multiple source directoriesGravatar Mike Burns2013-07-09
| | | | | | | | | | | | | | | | | | | | | | | The `rcup` and `mkrc` commands now support multiple source directories. This is useful for sharing dotfiles between friends, spliting dotfiles into private and public ones, or other such situations. In `mkrc` this support means that you can specify the destination directory for your dotfile, either from the command-line or from you `~/.rcrc` configuration. In `rcup` this means that it will recur through all source directories, in order, creating the symlinks as needed. This means that duplicated files will not be overridden. The order can be specified by the `-d` option, which can be repeated, or by the `DOTFILES_DIRS` option in your `~/.rcrc` configuration. The `-d` option overrides the configuration. For example, this configuration file will update from the two directories in order: DOTFILES_DIRS="/home/mike/.dotfiles/public /home/mike/.dotfiles/private" Any source directories that don't exist are skipped.
* Add a READMEGravatar Mike Burns2013-06-07
Introduce a README to describe the project, installation, support, and license.