[Slackbuilds-users] Tor needs recompile after libevent upgrade

[Kemal Ilgar Eroglu]

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,

Ilgar




>________________________________
>From: Ben Mendis <dragonwisard at gmail.com>
>To: Kemal Ilgar Eroglu <ilgar_eroglu at yahoo.com>; SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
>Sent: Tuesday, July 5, 2011 5:10 PM
>Subject: Re: [Slackbuilds-users] Tor needs recompile after libevent upgrade
>
>
>
>
>
>On Tue, Jul 5, 2011 at 9:50 AM, Kemal Ilgar Eroglu <ilgar_eroglu at yahoo.com> wrote:
>
>
>>
>>I sent the message below to the maintainer but got no reply, so I'm sending it to the list now:
>>
>>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)?
>
>
>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. 
> 
>Thanks,
>>
>> Ilgar
>>_______________________________________________
>>SlackBuilds-users mailing list
>>SlackBuilds-users at slackbuilds.org
>>http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>FAQ - http://slackbuilds.org/faq/
>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110705/21611846/attachment.html>