status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

make DEB package descriptions long (#4620) 

Apparently it's a good practice:
https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#the-long-description

Text mostly taken from https://nimbus.guide/.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
This commit is contained in:
Jakub Sokołowski 2023-02-14 17:51:52 +01:00 committed by GitHub
parent 32f6309f95
commit 4aae1f0ee8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
scripts/package_src/nimbus_beacon_node/description
View File

@ -1 +1,12 @@
Nimbus Beacon Node / Ethereum Consensus client
Nimbus is a client for the Ethereum network that is lightweight,
secure and easy to use.
.
Its efficiency and low resource consumption allows it to perform well
on all kinds of systems, ranging from Raspberry Pi's and mobile devices
where it contributes to low power consumption and security
-- to powerful servers where it leaves resources free to perform other tasks,
such as running an execution node.
.
The beacon node connects to the beacon chain network, syncs historical data
and provides API's to monitor and interact with the beacon chain.

13
scripts/package_src/nimbus_validator_client/description
View File

@ -1 +1,12 @@
Nimbus Validator Client
Nimbus Validator Client for Ethereum
Nimbus is a client for the Ethereum network that is lightweight,
secure and easy to use.
.
Its efficiency and low resource consumption allows it to perform well
on all kinds of systems, ranging from Raspberry Pi's and mobile devices
where it contributes to low power consumption and security
-- to powerful servers where it leaves resources free to perform other tasks,
such as running an execution node.
.
The validator client allows advanced users to run validators in a separate
process from the beacon node, allowing more flexible deployment strategies.