03-19-2020, 08:17 AM
@belfastraven : the name originally came from the culture, but I think it's certainly appropriately inappropriate for a repo like this one :D
I must've missed the re2-error on aarch64; I had already done a rebuild for x86_64 when it occured there, but with my PBP being down for a few days I didn't catch it there. A new version (80.0.3987.149-1) will be up in the repo in a short bit of time – the issue is fixed there.
@vrabac
I do intend to "consolidate" all the PKGBUILDs for all packages in one git repo, but at the moment they're still somewhat spread out. As @as400 mentioned, https://gitlab.com/ohfp/pinebookpro-things, https://gitlab.com/ohfp/caidao and https://gitlab.com/librewolf-community/browser/linux (and https://gitlab.com/librewolf-community/browser/arch) are the places to look for them.
I do encourage building things yourself. A repository just adds convenience, especially with large packages like chromium builds. Where possible, things are run in a Gitlab pipeline and can be reviewed even further (eg. https://gitlab.com/ohfp/caidao/-/jobs), but I could, of course, still fake a build and release/upload a different binary. This is, in the end, a matter of trust, and your threat model – so feel encouraged to grab the PKGBUILDs and use them as you please :)
I must've missed the re2-error on aarch64; I had already done a rebuild for x86_64 when it occured there, but with my PBP being down for a few days I didn't catch it there. A new version (80.0.3987.149-1) will be up in the repo in a short bit of time – the issue is fixed there.
@vrabac
I do intend to "consolidate" all the PKGBUILDs for all packages in one git repo, but at the moment they're still somewhat spread out. As @as400 mentioned, https://gitlab.com/ohfp/pinebookpro-things, https://gitlab.com/ohfp/caidao and https://gitlab.com/librewolf-community/browser/linux (and https://gitlab.com/librewolf-community/browser/arch) are the places to look for them.
I do encourage building things yourself. A repository just adds convenience, especially with large packages like chromium builds. Where possible, things are run in a Gitlab pipeline and can be reviewed even further (eg. https://gitlab.com/ohfp/caidao/-/jobs), but I could, of course, still fake a build and release/upload a different binary. This is, in the end, a matter of trust, and your threat model – so feel encouraged to grab the PKGBUILDs and use them as you please :)
