-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contributing bottles? #1175
Comments
I don't know about contributing built packages but I wonder if as a timesaver for those running with a stock setup and not experimenting with changes it would be helpful to make running lengthy testsuites optional, similar to Perl's formula. That would save a bunch for OpenSSL builds. |
See #1037, which updates openssl3 to 3.3.1 and makes the test suite run optional. Unless you're doing something other than using a stock configuration of OS X with matching XCode, you should be able to skip on having to run the test suite as I'll try to test those as part of the PR details. You'd need to run it if you're building with a different toolchain or experimenting. |
First of all, sorry for the delay getting back to you. I do think it'd be great to accept bottles from more sources! My main concern is just security: how to make sure all bottles are trustworthy if they don't come from me. I know that PowerPC Macs aren't exactly the biggest security target, but I'd like to be confident in knowing that all the binaries Tigerbrew publishes are safe. |
Is it possible to contribute precompiled bottles to the project? I'd be more than willing to do so if possible, especially for common dependencies/commonly installed formulae, to save the pain of other people having to spend ~111 minutes to compile OpenSSL on a G4 1.5GHz running Leopard.
The text was updated successfully, but these errors were encountered: