<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I've pm the user offering support.</p>
    <div class="moz-cite-prefix">On 9/26/25 07:54, Jeremy Hansen wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANi9qSvhSDpHMjn1KQOJJa+7+CBNzsYcPHRp0x_y_bswrgd0gQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">
        <div><br>
          <br>
          <div class="gmail_quote gmail_quote_container">
            <div dir="ltr" class="gmail_attr">On Thu, Sep 25, 2025,
              11:03 PM David Chmelik <<a
                href="mailto:davidnchmelik@gmail.com"
                moz-do-not-send="true" class="moz-txt-link-freetext">davidnchmelik@gmail.com</a>>
              wrote:<br>
            </div>
            <blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On
              9/25/25 7:31 PM, Willy Sudiarto Raharjo wrote:<br>
              >> /opt/google-chrome-the-latest .  Once I had maybe
              100+ GB of old .debs<br>
              >> in there so started running out of space...
              thanks to maintainer for<br>
              >> making it delete old ones.<br>
              > If you use sbopkg, you can use sbopkg -o to delete
              old sources<br>
              So that also deletes /opt/google-chrome-the-latest/*.deb?<br>
            </blockquote>
          </div>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">No, because sbopkg isn't what populates that
          directory. sbopkg uses /var/cache/sbopkg to download its
          sources and will clear that directory when passed when `-o`.
          It is not involved at all once your run
          /opt/google-chrome-the-latest and will require you to do any
          cleanup (since it doesn't seem to be provided by that scrip).
          The script included with the brave SlackBuild that has
          *absolutely nothing to do with SBo and tools that interact
          with SBo*.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Your grievances should only be taken up with the
          SlackBuild maintainer since they decided to include a script
          that allows building newer versions than included on SBo
          without cleaning up the previous sources and seems to be
          currently broken.. All this is outside the SBo admins' control
          since the SlackBuild itself works properly.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">The fact that this is an entirely separate
          script from the SlackBuild on SBo intrinsically removes any
          fault of that script from SBo and its admins and places it
          solely on the SlackBuild maintainer.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Jeremy</div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre wrap="" class="moz-quote-pre">_______________________________________________
SlackBuilds-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
Archives - <a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
FAQ - <a class="moz-txt-link-freetext" href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a>

</pre>
    </blockquote>
  </body>
</html>