@mistydemeo: here you mention you plan to bring your G5 box online. How will you secure your G5? I mean it would be irresponsible to just expose port 22 online, as it hasn't received any security updates in a long time (since 2009). I just bought an iMac G5 2.0 (early 2005), and I'd like to somehow help/contribute, but I'm always paranoid about it being pwned within minutes of connecting even to my home network.
Also, do you plan to have some sort of site with forum and/or IRC channel for tigerbrew? How do people discuss project issues that are not code related?
Is there some easy way to contribute G5 compute? I mean lets say someone has a spare G5 or even G4 box, and they use tigerbrew. Is there a single command that would somehow add it as a node in compile box? I imagine you'd want to have at least two compile boxes, controlled by two verified different contributors to produce matching bottles. It may be impossible if code contains __date__ or __time__ macros, but this way you can trust the results against malicious contributors or even simple non-ECC memory errors. It's actually a whole separate area - reproducible builds. Sorry if I'm overthinking/overdoing stuff :)
Also, please consider adding a link to troubleshooting to root wiki page
@mistydemeo: here you mention you plan to bring your G5 box online. How will you secure your G5? I mean it would be irresponsible to just expose port 22 online, as it hasn't received any security updates in a long time (since 2009). I just bought an iMac G5 2.0 (early 2005), and I'd like to somehow help/contribute, but I'm always paranoid about it being pwned within minutes of connecting even to my home network.
Also, do you plan to have some sort of site with forum and/or IRC channel for tigerbrew? How do people discuss project issues that are not code related?
Is there some easy way to contribute G5 compute? I mean lets say someone has a spare G5 or even G4 box, and they use tigerbrew. Is there a single command that would somehow add it as a node in compile box? I imagine you'd want to have at least two compile boxes, controlled by two verified different contributors to produce matching bottles. It may be impossible if code contains
__date__
or__time__
macros, but this way you can trust the results against malicious contributors or even simple non-ECC memory errors. It's actually a whole separate area - reproducible builds. Sorry if I'm overthinking/overdoing stuff :)Also, please consider adding a link to troubleshooting to root wiki page