<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 14/05/2019 13:40, Stephen John
      Smoogen wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANnLRdj6VRM=gLO2VBqrmUx=W_mKFk6UAZaAJj0k=+tfs-X4zw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Tue, 14 May 2019 at
            07:57, Jan StanÄ›k <<a href="mailto:jstanek@redhat.com"
              moz-do-not-send="true">jstanek@redhat.com</a>> wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">As the person in charge
            of maintaining updates for the rh-* SCLs,<br>
            I can say that I'm not shipping/caring about these once they
            are marked<br>
            as EOL; so from my POV, they can be removed if it is not
            desirable to<br>
            have them in the repositories.<br>
            <br>
            That being said, there is a possibility that a inter-SCL
            dependency will<br>
            break, as have happened last summer with rh-ror42
            (maintained at the<br>
            time) and rh-nodejs4 (EOL). Since upstream does not remove
            the<br>
            unmaintained packages from the repos, such dependencies
            won't be<br>
            discovered until someone does remove them.<br>
            <br>
            Basically, I'm in favor of removing the EOL SCLs, but it
            might break<br>
            non-EOL collections, which will take some time to fix.<br>
          </blockquote>
          <div><br>
          </div>
          <div>Is there a way to archive these versus remove them? That
            way people who are looking for them would know that they are
            EOL but they could make their own copy and maintain it
            themselves?</div>
          <div><br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Standard practice in the past has been to move expired things to
    vault.centos.org - for example
    <a class="moz-txt-link-freetext" href="http://vault.centos.org/centos/7.5.1804/sclo/x86_64/sclo/">http://vault.centos.org/centos/7.5.1804/sclo/x86_64/sclo/</a><br>
    <br>
    Trevor<br>
  </body>
</html>