When I read the following statement
The idea that we have for Coffee is to be the de facto tool to install and build a plugin in Core Lightning
I would expect to have plugins work out of the box but looks like dependencies are not installed but at least for official repo should be ?
Example:
Fresh install
$ coffe remote install backup
...
$ coffee list
● Plugin installed
╭──────────────────────────────────────────────────────────────────────────────────────╮
│ ● Language Name Exec path │
├──────────────────────────────────────────────────────────────────────────────────────┤
│ ● python backup /home/bitcoin/.coffee/repositories/official/backup/backup.py │
╰──────────────────────────────────────────────────────────────────────────────────────╯
Run
$ lightningd --network=bitcoin --log-level=debug
Traceback (most recent call last):
File "/home/bitcoin/.coffee/repositories/official/backup/backup.py", line 2, in <module>
from pyln.client import Plugin
ModuleNotFoundError: No module named 'pyln'
Expectation
I had to manually run pip3 install pyln-client but would expect to coffee handle this for me.
I would also somewhat expect to not need to go to backup dir and need to run.
./backup-cli init --lightning-dir ~/.lightning/bitcoin file:///mypath/lightning.bkp
When I read the following statement
I would expect to have plugins work out of the box but looks like dependencies are not installed but at least for official repo should be ?
Example:
Fresh install
Run
Expectation
I had to manually run
pip3 install pyln-clientbut would expect to coffee handle this for me.I would also somewhat expect to not need to go to backup dir and need to run.