From owner-cvs-ports Tue Aug 20 02:12:44 1996 Return-Path: owner-cvs-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA12193 for cvs-ports-outgoing; Tue, 20 Aug 1996 02:12:44 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA12144; Tue, 20 Aug 1996 02:11:54 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id CAA01466; Tue, 20 Aug 1996 02:11:32 -0700 (PDT) Date: Tue, 20 Aug 1996 02:11:32 -0700 (PDT) Message-Id: <199608200911.CAA01466@silvia.HIP.Berkeley.EDU> To: peter@spinner.DIALix.COM CC: jkh@time.cdrom.com, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-ports@freefall.freebsd.org In-reply-to: <199608191722.BAA15836@spinner.DIALix.COM> (message from Peter Wemm on Tue, 20 Aug 1996 01:21:59 +0800) Subject: Re: cvs commit: ports/devel/libz/pkg COMMENT DESCR PLIST ports/devel/libz Makefile ports/devel/libz/files md5 ports/devel/libz/patches patch-aa From: asami@freebsd.org (Satoshi Asami) Sender: owner-cvs-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Note that I left the "SHARED_LIB_SUFFIX" rules alone, this seems to be * what the tk port uses to generate it's name. Changing this will require * larger changes around the place, as "-ltk41" will become "-ltk" and * libtk41.so.1.0 will become libtk.so.41.0. Perhaps that's not such a bad * thing anyway. No, please leave these alone. We have discussed this on the ports list before, and the conclusion was: (1) Stuff in /usr/src should not use part of library name to denote library version. The shared library version can take care of it. (2) Stuff in /usr/ports that many other ports depend on should use part of library name to denote library version. The shlib version number should *not* be used for this purpose. (Just imagine trying to link libtcl.so.7.3 when there also is a libtcl.so.7.5.) This is because we have total control over what's in /usr/src, and can update every part of the system to use the new version when we change it. On the other hand, the ports tree is a mixed beast with a whole lot of things depending on the older version. * * * That said, the existence of libtcl.so.75.0 as tcl-7.5 has caused some problems in the ports tree. I'm not sure how well the stuff that depend on tcl-7.3 works now, can someone check it? (Especially how it's supposed to pick up the library -- since "-ltcl" now means "libtcl.so.75.0", not "libtcl.so.7.3".) Satoshi