Closed makew0rld closed 5 years ago
At the moment I would suggest a removal of the module, because it does not install at all right now. I am not in favour of using a very old version on Github instead.
@darkdrgn2k Thoughts on everything above?
Upstream patch no in PR to install correct Patchfoo install #400 not sure if it will work with version bump of Node.js
If you want to test it try git cherry-pick 107fae35f23363da38f7c5d0feadb5b0d9010190
before install
This has been hacked around because of #400, but still needs a real fix and Patchfoo update in the long run.
but still needs a real fix and Patchfoo update in the long run.
don't hold your breath this is the same issue we had with git-ssb from the beggining.
As I noticed here, Patchfoo can no longer be downloaded from Github, and shouldn't be either, even though there is a commit history.
Previously, Patchfoo would be downloaded from Github and refs to git-ssb would be removed, so that difficulty of installing that wouldn't be needed. Looking at the newer version of Patchfoo, it uses git-ssb a lot for displaying those kinds of messages, and that part of it can't simply be removed. For example, here's all the times
git
is mentioned in the Patchfoo source:So git-ssb will need to be installed. To install git-ssb, we also need to install ssb-npm, and ssb-npm-registry (also required directy by Patchfoo). All these installations need a connection to the SSB network during the installation, meaning that for us to install Patchfoo like this, ssb-server will already need to be installed and peered with a pub or two, and successfully synced everything.
This feels like a huge mess and a lot of work, so I made this issue before diving in. One solution might be to host the required blobs ourselves, so that an SSB network connection isn't required. But these blobs update and change all the time, and keeping track of them won't work very well and will just add another job for us.