Talk:Soname

Hi,

My last edit was a major one, since I believe the previous content was misleading. Feel free to revert or replace, but consider the following:

1. The soname is not only for versioning information. For examples, it is also used when several implementations (e.g. different vendors or different algorithms) provide the same interface.
2. The version numbering in the example is misleading, since typically changing the major version indicates a change of interface (so change of soname would be appropriate).
3. I believe using specific strings makes the example more clear.
4. I also added a reference.

--AmitAronovitch (talk) 12:32, 17 December 2008 (UTC)

Illogical?

"If the system only includes version 1.3 of that shared object, libx.so.1.3, the soname field of the shared object tells the system that it can be used to fill the dependency for a binary which was originally compiled using version 1.2."

But in the sentence before, it was stated that all versions between 1.0 and 1.9 could use the filename libx.so.1.

"In Unix operating systems, a soname is a field of data in a shared object file. The soname is a string (typically the filename of the library) [...]"

Is the filename considered being part of the data of a file?
Thanks, --Abdull (talk) 13:36, 10 December 2009 (UTC)

Changed "typically the filename" → "typically equal to the filename" plus other clarifications.

Hope that the answer (no) is clear from the current version of the text.

Thanks, --AmitAronovitch (talk) 09:33, 23 September 2010 (UTC)

I concur with the confusion in the discussion of version 1.3 vs. 1.2 . This really needs to be clarified. BMJ-pdx (talk) 09:23, 12 May 2018 (UTC)

Someone please fix the formatting

My apologies for the request.... The new editor completely f**k'd up the formatting of the discussion on linker flags -h and -soname. If someone knows how to use the new editor, please fix the mistakes. Jeffrey Walton 01:17, 27 July 2013 (UTC)