Re: The case of libkmod's .so versioning attempts, and induced collisions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/06/2012 06:35 PM, Jan Engelhardt wrote:
Much to my disappointment, I found that the newly-released libkmod v5
has made the following non-trivial change to its source tree, the latter
of which I want to bring to attention:

	commit e479598b7d19ae7be45bf5329d6e4df32d646c16
	diff --git a/Makefile.am b/Makefile.am
	index 69ab986..172d2ff 100644
	--- a/Makefile.am
	+++ b/Makefile.am
	-LIBKMOD_CURRENT=4
	+LIBKMOD_CURRENT=2
	 LIBKMOD_REVISION=0
	-LIBKMOD_AGE=3
	+LIBKMOD_AGE=0

It doesn't really make sense to use libtool at all in this situation, there is no portability requirement. Perhaps -version-number instead of -version-info would make their lives easier as it does the calculations for them.

Peter

--
To unsubscribe from this list: send the line "unsubscribe linux-modules" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux