<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">I see. Thanks!<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 13, 2016 at 11:02 PM, Willy Sudiarto Raharjo <span dir="ltr"><<a href="mailto:willysr@slackbuilds.org" target="_blank">willysr@slackbuilds.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Well, it looks like the same guy did it again in January. I thought only<br>
> the maintainer could submit updates to the slackbuild. Is that incorrect?<br>
><br>
> Since this appears to be happening, lets just go ahead and commit this<br>
> update. It eliminates the cumbersome patch files and gets us all the<br>
> latest bug fixes except for what's in the last release since that release<br>
> wont build and I haven't investigated why yet.<br>
<br>
</span>It was one of the admin, Matteo (ponce)<br>
During development cycle like this, we often update the SlackBuild if<br>
it's really needed for several reasons:<br>
- Fix a build failure due to changes in Slackware<br>
- Not yet updated by maintainer for a long time<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Willy Sudiarto Raharjo<br>
<br>
</font></span><br>_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" rel="noreferrer" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
<br></blockquote></div><br></div>