From 47adb693ac1c82a10a841e01b01edf5e530ebdcf Mon Sep 17 00:00:00 2001 From: Boyuan Yang <073plan@gmail.com> Date: Wed, 4 Nov 2015 12:23:56 +0800 Subject: [PATCH 1/2] update README for Debian/Ubuntu/Archlinux --- README.md | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fcb84d90..f430632f 100644 --- a/README.md +++ b/README.md @@ -64,15 +64,22 @@ sudo apt-get update sudo apt-get install shadowsocks-libev ``` -#### Build package from source +#### Build deb package from source Supported Platforms: * Debian 7 (see below), 8, unstable -* Ubuntu 14.10, 15.04 or higher +* Ubuntu 14.04 (see below), Ubuntu 14.10, 15.04, 15.10 or higher +**Note for Ubuntu 14.04 users**: +Packages built on Ubuntu 14.04 may be used in later Ubuntu versions. However, +packages built on Debian 7/8/9 or Ubuntu 14.10+ **cannot** be installed on +Ubuntu 14.04. + +**Note for Debian 7.x users**: To build packages on Debian 7 (Wheezy), you need to enable `debian-backports` to install systemd-compatibility packages like `dh-systemd` or `init-system-helpers`. +Please follow the instructions on [Debian Backports](http://backports.debian.org). This also means that you can only install those built packages on systems that have `init-system-helpers` installed. @@ -133,6 +140,14 @@ su -c 'yum update' su -c 'yum install shadowsocks-libev' ``` +### Archlinux + +```bash +sudo pacman -S shadowsocks-libev +``` + +Please refer to downstream `PKGBUILD` file for any extra modifications. + ### Linux For Unix-like systems, especially Debian-based systems, From 4f01d2f8d8941080e582ecf9557d2ced8a93bc1e Mon Sep 17 00:00:00 2001 From: Boyuan Yang <073plan@gmail.com> Date: Wed, 4 Nov 2015 12:25:30 +0800 Subject: [PATCH 2/2] fix a typo --- man/ss-server.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/ss-server.1 b/man/ss-server.1 index 05ad6181..81cca85d 100644 --- a/man/ss-server.1 +++ b/man/ss-server.1 @@ -118,7 +118,7 @@ Only available in server and manager mode. Enable verbose mode. .SH EXAMPLE -It is recommanded to use a config file when starting \*(Se(1). +It is recommended to use a config file when starting \*(Se(1). The config file is written in JSON and is easy to edit. Check out the \fBSEE ALSO\fR section for the default path of config file.