blob: edec8b45c6a406e8ad7091db034f83454096e69b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
post_install() {
update-desktop-database -q
printf "%b\n" "$bitcoin"
}
post_upgrade() {
update-desktop-database -q
printf "%b\n" "$bitcoin"
}
post_remove() {
update-desktop-database -q
}
read -d '' bitcoin <<'EOF'
########################################################################
########################################################################
## ##
## Bitcoin Classic ##
## ____________ ##
## ##
## New to 0.12, when no -rpcpassword is specified, the daemon now ##
## uses a special 'cookie' file for authentication. This file is ##
## generated with random content when the daemon starts, and deleted ##
## when it exits. Its contents are used as authentication token. ##
## Read access to this file controls who can access through RPC. By ##
## default it is stored in the data directory but its location can ##
## be overridden with the option -rpccookiefile. This is similar to ##
## Tor's CookieAuthentication. ##
## see: https://www.torproject.org/docs/tor-manual.html.en ##
## This allows running bitcoind without having to do any manual ##
## configuration. ##
## ##
########################################################################
########################################################################
EOF
|