3 ms·
>Just bite the bullet and run the 2h compilation process yourself. I don't think that's the best use of everyone's time or energy. Not to mention, it may be mo
by bubblethink 8y ago
>Just bite the bullet and run the 2h compilation process yourself.
I don't think that's the best use of everyone's time or energy. Not to mention, it may be more error prone, or even insecure depending on what your base system is like. And you'll have to track updates. It seems like chromium is problematic to build in general. Debian hasn't marked it as reproducible. It is also not clear if it is possible to build it for Android using a Foss stack. Various efforts to include chromium or derivatives in Fdroid have failed.
- eganist 8y ago> I don't think that's the best use of everyone's time or energy. Seems like there's a simple solution to this dilemma. Assuming build time is the single determining factor: If the value of two hours' build time overnight is less than the value of a privacy-enabled build of Chrome, then build Ungoogled Chromium overnight. Else, get Firefox.
- comex 8y agoSure, that's a solution if you think that running their binary is unacceptable. But that's begging the question. Most people running macOS (as vemv at least is) run a lot of random binaries from various types of strangers – mostly proprietary applications, although there's also things like Homebrew cached binaries, 'curl | sh' installers, etc. Now, in this case downloading a binary isn't necessary, since there's the option of building it yourself. That's great, and it's definitely (somewhat) safer to build it yourself... but that doesn't make the binary less trustworthy than if that weren't an option. If building sounds like too much effort, you shouldn't automatically give up on using the program, but just fall back to your personal baseline policy for running binaries. And for a lot of people, for better or worse, I think that policy is fairly trusting.
- vemv 8y agoAren't you forgetting the fact that binaries aren't provided by the project itself? They come from contributors (in the project's words: 'anyone'). That's wildly different from the typical CI-built binary.
- snaky 8y ago> Various efforts to include chromium or derivatives in Fdroid have failed. Fixed[1] in rattlesnakeos-stack[2] [1] https://www.reddit.com/r/RattlesnakeOS/comments/953dfj/v0025_latest_chromium_and_fdroid/ https://www.reddit.com/r/RattlesnakeOS/comments/953dfj/v0025... [2] "A cross platform tool that provisions all of the AWS infrastructure required to build your own privacy focused Android OS on a continuous basis with OTA updates." https://github.com/dan-v/rattlesnakeos-stack https://github.com/dan-v/rattlesnakeos-stack
- voltagex_ 8y agoHeh, I wonder how much that costs. You certainly don't want to be building the whole Android tree on the free tier. Edit: that's really well done - https://github.com/dan-v/rattlesnakeos-stack#how-much-does-this-cost https://github.com/dan-v/rattlesnakeos-stack#how-much-does-t...
- snaky 8y agoYes, that's well done. But it would be nice to port RattlesnakeOS build system from AWS to e.g. Nextcloud - because you pay for your Nextcloud VPS anyway, most of the time it's doing nothing, and most of the time you don't really care would it build in 2 hours or 2 days.
- voltagex_ 8y agoI don't know enough Go - but it'd be awesome to port it to packet.net in particular for the 24 core Epyc boxes. Most people's VPS won't have enough RAM to run the Android builld process.
- danvittegleo 8y agoIf you were looking to just do something similar but running on another platform, knowledge of Go isn't required. The core build process is a shell script, which just has some variables injected through Go templates: https://raw.githubusercontent.com/dan-v/rattlesnakeos-stack/9.0/templates/build_template.go https://raw.githubusercontent.com/dan-v/rattlesnakeos-stack/...