diff options
| -rw-r--r-- | .SRCINFO | 4 | ||||
| -rw-r--r-- | PKGBUILD | 4 | ||||
| -rw-r--r-- | conf.yml | 25 |
3 files changed, 17 insertions, 16 deletions
@@ -1,7 +1,7 @@ pkgbase = cheat pkgdesc = Allows you to create and view interactive cheatsheets on the command-line pkgver = 3.7.0 - pkgrel = 1 + pkgrel = 2 url = https://github.com/cheat/cheat arch = arm arch = armv6h @@ -24,7 +24,7 @@ pkgbase = cheat source = git+https://github.com/cheat/cheatsheets.git source = https://raw.githubusercontent.com/cheat/cheatsheets/master/.github/LICENSE.txt sha256sums = aa598370694ef5e96fc6d4d1957635207206bd394613e9e1760146e8c79ff123 - sha256sums = d2f0e84c1fccb5916ee42d1696f04aa998aee30fb0173dbbe40926e770fe5bfd + sha256sums = 89bb38469a5a71c25d1f37cf1d7a2a7216b1b0bde01b4d3c630bcc48d498f74e sha256sums = SKIP sha256sums = a2010f343487d3f7618affe54f789f5487602331c0a8d03f49e9a7c547cf0499 @@ -3,7 +3,7 @@ # Contributor: Bogdan <d0xi at inbox dot ru> pkgname=cheat pkgver=3.7.0 -pkgrel=1 +pkgrel=2 pkgdesc="Allows you to create and view interactive cheatsheets on the command-line" arch=('arm' 'armv6h' 'armv7h' 'x86_64') url="https://github.com/cheat/cheat" @@ -20,7 +20,7 @@ source=("$pkgname-$pkgver.tar.gz::https://github.com/$pkgname/$pkgname/archive/$ "git+https://github.com/$pkgname/cheatsheets.git" "https://raw.githubusercontent.com/$pkgname/cheatsheets/master/.github/LICENSE.txt") sha256sums=('aa598370694ef5e96fc6d4d1957635207206bd394613e9e1760146e8c79ff123' - 'd2f0e84c1fccb5916ee42d1696f04aa998aee30fb0173dbbe40926e770fe5bfd' + '89bb38469a5a71c25d1f37cf1d7a2a7216b1b0bde01b4d3c630bcc48d498f74e' 'SKIP' 'a2010f343487d3f7618affe54f789f5487602331c0a8d03f49e9a7c547cf0499') @@ -32,11 +32,12 @@ cheatpaths: # thus be overridden by more local cheatsheets. That being the case, you # should probably list community cheatsheets first. # - # Note that the paths and tags listed below are just examples. You may freely + # Note that the paths and tags listed below are placeholders. You may freely # change them to suit your needs. # - # TODO: regarding community cheatsheets: these must be installed separately. - # You may download them here: + # Community cheatsheets must be installed separately, though you may have + # downloaded them automatically when installing 'cheat'. If not, you may + # download them here: # # https://github.com/cheat/cheatsheets # @@ -49,16 +50,16 @@ cheatpaths: # If you have personalized cheatsheets, list them last. They will take # precedence over the more global cheatsheets. - #- name: personal - # path: ~/cheat/cheatsheets/personal - # tags: [ personal ] - # readonly: false + - name: personal + path: PERSONAL_PATH + tags: [ personal ] + readonly: false - # While it requires no specific configuration here, it's also worth noting - # that 'cheat' will automatically append directories named '.cheat' within - # the current working directory to the 'cheatpath'. This can be very useful - # if you'd like to closely associate cheatsheets with, for example, a - # directory containing source code. + # While it requires no configuration here, it's also worth noting that + # 'cheat' will automatically append directories named '.cheat' within the + # current working directory to the 'cheatpath'. This can be very useful if + # you'd like to closely associate cheatsheets with, for example, a directory + # containing source code. # # Such "directory-scoped" cheatsheets will be treated as the most "local" # cheatsheets, and will override less "local" cheatsheets. Likewise, |