cvs commit: ports/polish/kadu Makefile distinfo pkg-descr pkg-plist ports/polish/kadu/files patch-kadu-core__CMakeLists.txt patch-kadu-core_gadu_resolver.cpp patch-modules__docking__CMakeLists.txt patch-modules__idle__CMakeLists.txt patch-modules__kde_notify__CMakeLists.txt patch-modules__screenshot__CMakeLists.txt patch-modules__sound__CMakeLists.txt ...

[Doug Barton]

On 08/22/2011 19:42, Alexey Dokuchaev wrote:
> On Mon, Aug 22, 2011 at 07:19:18PM -0700, Doug Barton wrote:
>>> bumping port revision of library consumer ports to chase shlib version
>>> bumps.
>>
>> The version should only be specified for dependents that are tied to a
>> specific version. If the dependent can survive a version bump of the lib
>> then the dependency should be specified without version, and NOT bumped
>> when the lib is updated.
> 
> I believe it will take too much work to verify which parts of the API port
> uses and either add or remove this suffix on every update. 

It's up to the maintainer to do this work, and handle the consequences.
I've done it for my ports. Those who don't wish to do this work can
simply add the specific version.

There are of course things that need to be consistent, but forcing
consistency where it's not necessary is not only not helpful, but can
cause more problems then it solves.

> We should uphold upstream decision (assuming they are not complete idiots to
> bump shlib version with no good reason) 

Yeah, cuz that's never happened before. :)


-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/