<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Ok then. For most updates you can continue to use the depending software without recompiling, but in this case Tor gets broken, so I thought a bump would be worth -- but if that was the decision then it's fine,</span></div><div><br><span></span></div><div><span>Ilgar<br></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Ben Mendis <dragonwisard@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Kemal Ilgar Eroglu <ilgar_eroglu@yahoo.com>; SlackBuilds.org Users List
<slackbuilds-users@slackbuilds.org><br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, July 5, 2011 5:10 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Slackbuilds-users] Tor needs recompile after libevent upgrade<br></font><br>
<div id="yiv1952724325"><br><br><div class="yiv1952724325gmail_quote">On Tue, Jul 5, 2011 at 9:50 AM, Kemal Ilgar Eroglu <span dir="ltr"><<a rel="nofollow" ymailto="mailto:ilgar_eroglu@yahoo.com" target="_blank" href="mailto:ilgar_eroglu@yahoo.com">ilgar_eroglu@yahoo.com</a>></span> wrote:<br><blockquote class="yiv1952724325gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
I sent the message below to the maintainer but got no reply, so I'm sending it to the list now:<br>
<br>
libevent in the repo has been upgraded from 1.4 to 2.0 and this requires Tor to be recompiled against the new version. Could you bump the build number to -2 in the Slackbuild (so that it gets updated as well)?</blockquote>
<div><br></div><div>I remember a similar discussion on the this list around the time 13.37 was being prepared. The consensus was that build numbers should not be arbitrarily bumped because a dependency has been upgraded. They represent the version number of the SlackBuild itself, they are not a mechanism for dependency tracking. </div>
<div> </div><blockquote class="yiv1952724325gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Thanks,<br>
<br>
Ilgar<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a rel="nofollow" ymailto="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users<br>
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/<br>
FAQ - http://slackbuilds.org/faq/<br>
<br>
</blockquote></div><br>
</div><br><br></div></div></blockquote></div></div></body></html>