Open randomshinichi opened 3 years ago
this is a fantastic idea. let me know if I can be of any help
this is a fantastic idea. let me know if I can be of any help
Thanks man, can you write Ruby? I've made a fork over at https://github.com/randomshinichi/tigerbrew, let's talk there
I have got a microservice running with a HTTP API but I need to figure out how to make sha-summing not lock up the server. also how to keep the shasums up to date with the packages.
Unfortunately I don't. I'm open to learn, though, if there's simple stuff I could contribute to. FWIW, I do code python, and some C / C++, if it's any help.
On Thu, Mar 4, 2021 at 12:19 PM Andrew Chiw notifications@github.com wrote:
this is a fantastic idea. let me know if I can be of any help
Thanks man, can you write Ruby? I've made a fork over at https://github.com/randomshinichi/tigerbrew, let's talk there
I have got a microservice running with a HTTP API but I need to figure out how to make sha-summing not lock up the server. also how to keep the shasums up to date with the packages.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mistydemeo/tigerbrew/issues/719#issuecomment-790693934, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDVDOMWR6F5G5DT3DYU4JTTB6QHHANCNFSM4WP6LW6Q .
There's been a lot of updates recently, and there's more updates to come.
Currently, the bottles hosted on https://archive.org/download/tigerbrew are outdated, so I have to compile everything myself. It is obvious that tigerdemeo alone cannot maintain everything, and thus something must be done to spread and even incentivize work across the community.
Proposal: When Tigerbrew is first setup, it prompts for the user's "nickname", and whether to upload bottles if a Formula finishes compiling. If the user agrees, bottles are uploaded to a temporary repository. If the sha256sum already exists, it is not uploaded. A simple microservice can be written here, and I can provide some storage.
The nickname is used to give credit for the upload. Let's say 1 point for each bottle uploaded. Sounds silly but it works: look at Folding@Home points, which are worthless but people still buy graphics cards to top the charts.
Thus the problem of compiling binaries for different architectures and OSX versions is spread across the community automatically.
The temporary repository is used for some semblance of control over the binaries (in case someone tries to upload malware or whatever). IPFS can solve the problem of hosting. People with little technical knowhow can be told they can still contribute to this project simply by running a IPFS node and gateway that hosts the bottles. Periodically we will need to delete old bottles. IPFS nodes can independently choose to keep the old bottles or follow the crowd and save disk space.
I'd be happy to help. I don't want to compile stuff on my iBook anymore. I just want to use it.