Archiving this repo?

[jakirkham]

Would like to suggest we archive this repo. The content here should already be handled by the (new) compilers and associated runtime libraries. It also seems to be confusing users a bit. So it might be worth leaving a note in the README or the repo description explaining this before archiving. Thoughts?

cc @conda-forge/core

[asmeurer]

I think archiving disables issues, so if you do so, you should have a pointer for where to go if people have issues.

Also, unless this has been fixed in conda since I last tried, removing libgfortran breaks gcc because it installs the same package. So to remove it properly you have to also uninstall and reinstall gcc. That would be worth mentioning in the README.

[jakirkham]

I think archiving disables issues, so if you do so, you should have a pointer for where to go if people have issues.

Yep, this seems like good info to have in the README or the description note.

Also, unless this has been fixed in conda since I last tried, removing libgfortran breaks gcc because it installs the same package.

This is exactly the sort of confusion that we need to avoid. No one should be installing the gcc package. It is unmaintained, unused, and ABI incompatible with conda-forge packages. Only the (new) Anaconda compilers should be used.

[asmeurer]

As long as the package is there people will install it. What is the correct replacement?

[isuruf]

This package is still used in OSX until we switch to a newer gfortran.

[jakirkham]

Is that true? I think people are getting libgfortran-ng. For example like here.

[isuruf]

That's a linux_ppc64le build. Not OSX

[jakirkham]

Apologies. Was misled by the badge.