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 <[email protected]>
>To: Kemal Ilgar Eroglu <[email protected]>; SlackBuilds.org Users List
><[email protected]>
>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 <[email protected]>
>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
>>[email protected]
>>http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>FAQ - http://slackbuilds.org/faq/
>>
>>
>
>
>
_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
