Date: Thu, 23 Sep 1999 10:39:44 +0200 From: Marcel Moolenaar <marcel@scc.nl> To: Dmitrij Tejblum <tejblum@arc.hq.cti.ru> Cc: Nate Williams <nate@mt.sri.com>, cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/secure/lib/libcrypt Makefile src/lib/libcrypt Makefile Message-ID: <37E9E750.85237877@scc.nl> References: <199909222151.BAA05460@tejblum.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Dmitrij Tejblum wrote: > > Nate Williams wrote: > > > > No, you'd rather everyone be confused as to *which* version of > > > > libcrypt.so.1 is the correct version? With your solution, there could > > > > be *dozens* of files with the same name that are very different from one > > > > another, and only the 'latest' version is correct. > > > > > > This is normal for every program in the system. You don't have a > > > version number on cat(1) or login(1). > I repeat again: this "breakage" is normal and have nothing specific to shared > libraries: > > Your /bin/sh is older than mine. If you install yours on my box, some > my shell script will no longer work (e.g. my shell script use new > 'read -r'). [snip] This is comparing apples with peers. Interpreters either supply versioning information to the source code or they don't. If they do, then it should be used to handle incompatibilities in a user friendly way. I they don't, then you obviously don't have a choice, other than writing backwards compatible code as much as possible. Shared libraries have versioning information. Use it! Don't start the versioning discussion all over again. Instead, continu the discussion on -hackers, please. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37E9E750.85237877>