Message 47064 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Recipients
Author	hyeshik.chang
Date	2004年10月26日.06:21:59
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=55188 Sorry for late reply, jwpye. Whether ldconfig(1) can catch a shared library or not can be not so important if all applications detect by trying linkings with explicit path or -L option. But, even FreeBSD ports uses ldconfig(1) to track dependency and ports prohibits installing shared libraries with dotted versions. (you can define NO_FILTER_SHLIBS=yes to avoid the rule.) In fact, FreeBSD developers are discussing internally about allowing lib*.so.major.minor versions for base shared libraries like libc. But Python tends to keep perfect ABI compatibility within branches and shared library major versions are virtually useless for Python. So, I think we can use just ".1" in FreeBSD anyways.

Content

Logged In: YES 
user_id=55188
Sorry for late reply, jwpye.
Whether ldconfig(1) can catch a shared library or not can be
not so important if all applications detect by trying
linkings with explicit path or -L option. But, even FreeBSD
ports uses ldconfig(1) to track dependency and ports
prohibits installing shared libraries with dotted versions.
(you can define NO_FILTER_SHLIBS=yes to avoid the rule.)
In fact, FreeBSD developers are discussing internally about
allowing lib*.so.major.minor versions for base shared
libraries like libc. But Python tends to keep perfect ABI
compatibility within branches and shared library major
versions are virtually useless for Python. So, I think we
can use just ".1" in FreeBSD anyways.

History
Date	User	Action	Args
2007年08月23日 15:40:11	admin	link	issue1044395 messages
2007年08月23日 15:40:11	admin	create

homepage