<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt"><div><span><br></span></div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> On Friday, August 22, 2014 8:32 AM, Ryan P.C. McQuen <ryanpcmcquen@gmail.com> wrote:<br> </font> </div> <br><br> <div class="y_msg_container"><div id="yiv1904350172"><div><div><blockquote type="cite"><span style="">Maybe <a rel="nofollow" shape="rect" target="_blank" href="http://slackbuilds.org/">slackbuilds.org</a> can adopt a similar policy?</span><br
clear="none"></blockquote><br clear="none"><div style="">I prefer staying on the latest version personally. The features they add with each new release are exciting to watch.</div><div style=""><br clear="none"></div><div style="">Modifying the build is easy enough, but it is nice for people using sbopkg to be able to automatically install the latest version. ;^)</div><div style=""><br>-----------<br><br clear="none"></div>Alternatively, SBo could host a "fresh" and a "still" version for the respective newest branch and just prior branch. This is how the LibreOffice site separates their downloads. It wouldn't be the first piece of software with two SlackBuilds for different versions.<br><br>--phillip<br></div></div></div></div> </div> </div> </div> </div></body></html>