<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>
      <blockquote type="cite">Ideally, I'd also have to repack and
        reupload earlier 0.5-x versions, as I did it wrong and didn't
        upload the linux capital letter aliases... how would that go if
        it's immutable? Seems too extreme for me and there could be good
        reasons to reupload a package at least when they screw up. And
        what if you have a typo? </blockquote>
      If you want to fix an existing older version (= backporting), you
      would usually do a new bugfix release for that version. For
      example, to fix 0.4.10, you would make a bugfix 0.4.11.</p>
    <p>That being said, often it's sufficient to just fix the latest
      version and ask people to upgrade. Backporting only makes sense if
      you need/want to support existing, possibly incompatible versions
      of programs/libraries, where upgrades are non-trivial. A good
      example are operating systems.<br>
    </p>
    <p>Christof<br>
    </p>
    <div class="moz-cite-prefix">On 20.10.2020 22:36, Alexandre Torres
      Porres wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAEAsFmgvyXwuTFY7Y1_zdysVxzhrKsSa7TNR08OTcDsed=BaSw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">
          <p class="gmail-p1"
style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span
              class="gmail-s1"
              style="font-variant-ligatures:no-common-ligatures"></span></p>
        </div>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">Em ter., 20 de out. de 2020
            às 03:34, IOhannes m zmoelnig <<a
              href="mailto:zmoelnig@iem.at" moz-do-not-send="true">zmoelnig@iem.at</a>>
            escreveu:</div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            > Tried in the makefile and it didn't work, but then I
            thought you may have<br>
            > meant when doing "make install" and it worked ;)<br>
            <br>
            i don't know what you tested.<br>
            but you should pass the "extension=..." argument to all</blockquote>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex"> invocations of make<br>
          </blockquote>
          <div><br>
          </div>
          <div>I did <b>make install objectsdir=../ extension=d_fat </b>and
            pd-lib-builder generated binaries with that extension.</div>
          <div> </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            > I just want to be clear there's no reason to keep it.
            If my previous<br>
            > package is better in any way or something (like
            "faster"?). <br>
            <br>
            the package is smaller.<br>
          </blockquote>
          <div><br>
          </div>
          <div>I see! Not enough a good reason for me to also compile it
            that way though...</div>
          <div><br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            if you want to avoid confusion totally (because you are
            friendly and <br>
            don't want to impose *any* mental stress onto people),
            upload a new version.</blockquote>
          <div><br>
          </div>
          <div> I get it. Well, I'm talking about cyclone, which I made
            a release on the 17th and on the 19th I had the other
            binary... that's too soon and too little for a new release.
            And yeah, I do think it's an unnecessary confusion/stress,
            not everyone knows the difference and might not know what to
            pick.</div>
          <div> </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">in general i think you
            should consider the deken storage as immutable </blockquote>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">("don't even think of
            trying to modify and/or delete stuff once published"). </blockquote>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">i would love to enforce
            this on the server-side, but it's very low on my </blockquote>
          <div><br>
          </div>
          <div>Still about cyclone, I just released 0.5-4! Ideally, I'd
            also have to repack and reupload earlier 0.5-x versions, as
            I did it wrong and didn't upload the linux capital letter
            aliases... how would that go if it's immutable? Seems too
            extreme for me and there could be good reasons to reupload a
            package at least when they screw up. And what if you have a
            typo? </div>
          <div><br>
          </div>
          <div>Anyway, I'm too busy and lazy to repack and reupload
            cyclone anyway.</div>
          <div><br>
          </div>
          <div>cheers</div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
<a class="moz-txt-link-abbreviated" href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list
UNSUBSCRIBE and account-management -> <a class="moz-txt-link-freetext" href="https://lists.puredata.info/listinfo/pd-list">https://lists.puredata.info/listinfo/pd-list</a>
</pre>
    </blockquote>
  </body>
</html>