Opened 5 months ago

Closed 5 months ago

Last modified 5 months ago

#70271 closed enhancement (wontfix)

openssl3: do not build tests by default, it takes ridiculous amount of time

Reported by: barracuda156 Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.9.3
Keywords: Cc: larryv (Lawrence Velázquez), neverpanic (Clemens Lang)
Port: openssl3

Description

Could we avoid building tests for openssl3 3.3.x by default? It takes ungodly time for compilation, and that is on G5 Quad. I can only imagine how someone with a G4 curses his life now.

Change History (4)

comment:1 Changed 5 months ago by neverpanic (Clemens Lang)

Don't we have binaries pretty much everywhere for OpenSSL?

comment:2 in reply to:  1 Changed 5 months ago by barracuda156

Replying to neverpanic:

Don't we have binaries pretty much everywhere for OpenSSL?

We do not have for 10.4 and 10.5, any arch.

comment:3 Changed 5 months ago by neverpanic (Clemens Lang)

Resolution: wontfix
Status: newclosed

Those are very old systems, which I don't support. My personal maintenance policy matches that of the project, which is (current-3;current).

I do run the tests when updating OpenSSL to new versions now, so if you want to submit a PR that disables building them, please do so in a way that disables them on old systems only, or provide a way for them to be built when the test target is executed (I believe this may be possible by changing build.target and test.target slightly).

I will not be spending time on this, so I'm going to close this as wontfix now, but I'm happy to accept pull requests.

comment:4 Changed 5 months ago by barracuda156

IMO it would be useful to have it opened, just remove assignment to yourself. (The issue itself is fixable and worth fixing.)

I will look into fixing it in coming days.

  1. S. It is actually a pretty standard practice not to build tests, unless test target is run. Unrelated to old OS – it is still wasteful, even if the extent is smaller.
Last edited 5 months ago by barracuda156 (previous) (diff)
Note: See TracTickets for help on using tickets.