Aliases: add openssl

[fxcoudert]

Following #46876, should we make openssl an alias for [email protected]? Is this breaking things for people who have the older formula installed?

Edit: the technical question is not “is this desirable?”, but “would this break things for some users?”. Input needed from experts in how brew code itself will handle this situation.

[austinirvine]

Yeah, I think openssl should be made an alias for 1.1. I think it would make a lot of sense for the latest, most stable release of openssl to point back to openssl formula. Users should be able to determine which version they want to use by simply deciding which version of the openssl formula they want to use. Most other formulas work this way. I think it would cause far less hassle for developers. -- I've been running into problems all day with openssl come to find out that the formula is gone. This could be a bit baffling to newbies given that most answers/tutorials on the web point back to the openssl formula. It definitely changes the process flow of work where I'm at as well.

[lhazlewood]

FWIW, on most (all?) major Linux distros (and for sure CentOS and Ubuntu), the package name for default openssl installs is just openssl. It'd be nice for Homebrew to use the same so we don't have to differentiate between distributions to determine which package to install. So this PR has a nice 👍 from me :)

[iMichka]

I'm am fine with the alias, if it helps some people. I have no clue about the technical implications though.

If we go the alias route, does this mean the situation will stay like this forever. Or does this leave us the opportunity to rename the file and revision bump everything later?

[fxcoudert]

Local tests seem to say it's fine with preexisting OpenSSL 1.0 installed as openssl. So… let's go!

[ergl]

How does this affect people with OpenSSL 1.0? If I install the new openssl package while still having the old one, will something break?

[Bo98]

It depends a bit if you have anything that needs 1.0. Certainly nothing in homebrew-core alone requires OpenSSL 1.0 anymore.

[ronisbr]

In fact, I think MSSQL ODBC driver requires openssl 1.0. I have a new installation that I cannot use this driver because a file for openssl 1.0 is missing. How can I install the older version?

[Bo98]

There's an upstream discussion about that: microsoft/homebrew-mssql-release#37. 1.1 should work according to them but perhaps you can help them debug.

[MikeMcQuaid]

The supported way to still use OpenSSL 1.0 is to use brew extract. brew installing from a URL is insecure and will break.