<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Excuse the terrible typos. See the corrected version below.<br>
    </p>
    <div class="moz-cite-prefix">On 24.11.2021 17:12, Christof Ressi
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:1ee41fb1-732f-1b03-f8f2-7c5c7af0a533@christofressi.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p>Hi,</p>
      <p>it's very common to upload test releases to Deken. They usually
        have suffixes like "alpha", "beta", "pre", "test" in their
        version number to make it clear that they are not stable
        releases. Pd users are really used to install any externals with
        Deken. Manual downloads are really the exception nowadays.<br>
      </p>
      <p>Care needs to be taken that the final release is ordered
        *before* the test releases by having a lexicographically
        *larger* version number. For example, "v0.1" is smaller than
        "v0.1-test" (= bad).</p>
      <p>To circumvent this problem, Deken sorts "~" before everything
        else, so you can safely use "v0.1~test". The only caveat is that
        "~" is not allowed in git tags, which can be a problem for
        certain CI setups where the version number is derived from the
        git tag.<br>
      </p>
      <p>Another trick is to include a bug fix number for the final
        release: "v0.1.0" ranks higher than "v0.1-test"</p>
      <p>Christof<br>
      </p>
      <div class="moz-cite-prefix">On 24.11.2021 16:55, Iain Duncan
        wrote:<br>
      </div>
      <blockquote type="cite"
cite="mid:CAN9NcLyKFscLfULrVSQPp=f_5S3i5NS-wumVLcAPzD8woS2v4A@mail.gmail.com">
        <meta http-equiv="content-type" content="text/html;
          charset=UTF-8">
        <div dir="ltr">Hi, yes they will be added to the package
          manager, in due time. Perhaps I'm in a minority here, but my
          perspective from a couple of decades of doing software is that
          package managers should only hold releases that are definitely
          stable and production ready.  One only has one chance for a
          first impression, and if new users hit problems with something
          in a package manager, it reflects badly on the project. When
          they hit the same issues after downloading a package marked
          "beta" from GitHub, it's quite a different impression. My
          opinion is that what I get from NPM or PyPi better "just
          work". :-)
          <div><br>
          </div>
          <div>So I need some reports from people on windows that
            installation and first steps are going smoothly, and then I
            will put it up in Deken. I would imagine it should be up in
            the next month.</div>
          <div><br>
          </div>
          <div>iain</div>
          <div><br>
          </div>
          <div><br>
          </div>
          <div><br>
          </div>
          <div><br>
          </div>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Wed, Nov 24, 2021 at 7:21
            AM IOhannes m zmölnig <<a href="mailto:zmoelnig@iem.at"
              moz-do-not-send="true" class="moz-txt-link-freetext">zmoelnig@iem.at</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">On 11/24/21 11:07, Peter
            P. wrote:<br>
            > unless you have already done this, do you think of
            adding these binaries<br>
            > to Pd's "Deken" Package manager?<br>
            <br>
            <br>
            <a
              href="https://github.com/iainctduncan/scheme-for-pd/issues/22"
              rel="noreferrer" target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">https://github.com/iainctduncan/scheme-for-pd/issues/22</a><br>
            <br>
            mfdsar<br>
            IOhannes<br>
            _______________________________________________<br>
            <a href="mailto:Pd-list@lists.iem.at" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">Pd-list@lists.iem.at</a>
            mailing list<br>
            UNSUBSCRIBE and account-management -> <a
              href="https://lists.puredata.info/listinfo/pd-list"
              rel="noreferrer" target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">https://lists.puredata.info/listinfo/pd-list</a><br>
          </blockquote>
        </div>
        <br>
        <fieldset class="moz-mime-attachment-header"></fieldset>
        <pre class="moz-quote-pre" wrap="">_______________________________________________
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:Pd-list@lists.iem.at" moz-do-not-send="true">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" moz-do-not-send="true">https://lists.puredata.info/listinfo/pd-list</a>
</pre>
      </blockquote>
      <br>
      <fieldset class="moz-mime-attachment-header"></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>