<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Alex,</p>
<p>just to sum up and emphasize what Roman has been saying: it's
good practice to keep old releases around, because existing
projects might depend on it. This is especially relevant in the
case of "else", since there are breaking changes between beta
versions.</p>
<p>Of course, you're free to tell users to get old releases from
GitHub, but IMO this defeats the purpose of Deken.</p>
<p>As Roman mentioned, Deken shows the library in decreasing order
of the version number. To get the most recent version, people just
have to click the first entry.</p>
<p>So please consider not removing "else" releases from Deken in the
future.<br>
</p>
<p>Christof<br>
</p>
<div class="moz-cite-prefix">On 08.06.2020 09:27, Roman Haefeli
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8b58a66ca4c988e1fa62db4b4c71cc282af9978f.camel@gmail.com">
<pre class="moz-quote-pre" wrap="">On Sun, 2020-06-07 at 19:34 -0300, Alexandre Torres Porres wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">The reason now, like I told you, is that I was/am trying to merge
into the same download the inclusion of my tutorial as a single combo
pack... so I put it down and tried to reupload but failed.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I see. What I'm actually suggesting is to do not touch already released
versions at all. If you make changes, then it should have a new version
and you should create a new release for this new version. At least that
is how I think releases should be handled and it seems already common
practice in Deken (and probably everywhere else in the software world).
Of course, you're free to do whatever you want with your software.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
I've been asked before to keep old stuff and we discussed this
before, and I agreed it wouldn't hurt to keep not that many old
versions around. It gets to a point where things change so much and
so quickly that I just thought it was too much pollution to keep old
stuff around
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I don't see the problem of pollution as long as you release new
versions with a higher version number (which you do). Newest version
appears on top in Deken. Right now, Deken provides the ELSE library
only for two architectures.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> so I had this policy. But the thing now is that I'm trying to do
this, and it got out of hand and over complicated, sorry.
But it seems now I'm being able to do it, let's see it in a day.
I can also just put the last version back if you give me a moment,
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
You don't have put stuff back solely for me.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">and I'm still curious, how does your script work? Can you please tell
me more about your needs?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Actually, I shouldn't have mentioned my script. It's not relevant to
the discussion. My point is to not confuse regular users of the
library. I think they should have easy access to previous versions when
they develop their patches dependent on the library, for instance for
testing regressions.
My script simply downloads the library from a configured URL and
extracts it to the right place, nothing fancy [1].
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Actually, I'm also now concerned if this script will work with my
attempt to pack two folders into a single download for deken.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Again, you should not be concerned about my script, but about regular
users.
Roman
[1] I got many complaints about how hard is to install netpd, that's
why I'm trying to create standalone applications for macOS and Windows
with Pd+externals+netpd+instruments bundled. The script also downloads
and extracts the ELSE library.
</pre>
<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>