DevHeads.net

What to do with SCLo SIG content that is EOL

We discussed this on last SCLo SIG sync-up meeting -- unlike packages
from CentOS base, SCL packages are not moving to Vault repos at this
point, although some of them are already EOL and not getting any
updates. A question was raised whether such packages should be moved to
Vault.

Comparing to CentOS base packages, SCL is different in packages naming
-- version of the stack is part of the package name. That means, that
once e.g. devtoolset-3 got EOL, yum won't update them ever, even though
there are some newer versions available (those use different name though)..

Moving such packages from mirrors to Vault would basically mean some
setups will get broken for users.

It's understandable, that some users are still fine using EOL packages,
but they would need to change repos to the Vault url.

What do you think -- should we start moving EOL SCLs into Vault? How big
problem would that be for you?

Honza