Date: 26 Dec 2001 09:21:08 +0900 From: NIIMI Satoshi <sa2c@and.or.jp> To: Dag-Erling Smorgrav <des@ofug.org> Cc: stable@freebsd.org, obrien@freebsd.org Subject: Re: libfetch.so.2 should be included in src/lib/compat/compat4x.* Message-ID: <20011226002108.6851B55@berkeley.sa2c.net> In-Reply-To: <xzp3d1zm7gs.fsf@flood.ping.uio.no> References: <20011223143139.97F8AFB@berkeley.sa2c.net> <xzpwuzdact2.fsf@flood.ping.uio.no> <20011225040025.7A99322B@berkeley.sa2c.net> <xzp3d1zm7gs.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav <des@ofug.org> writes: > The only libfetch consumers (that I know of) are fetch(1) and the pkg > tools. Old binaries will still work on an upgraded system (which will > still have libfetch.so.2) but not on a fresh install (which will lack > libfetch.so.2), but both upgraded and freshly installed systems will > have up-to-date versions of fetch(1) and the pkg tools. Because fetch(3) is very reasonable (I thank you, DES), I wrote some programs that use libfetch and the programs have some non-experienced users. When the guys will deploy new 4.5-RELEASE systems, they will confuse and contact me because the programs does not work even with compat libraries. I don't want such a waste of time. > Moreover, libfetch.so.3 is backward compatible, so a symlink should be > sufficient to support old binaries. The reason for the bump is that > new binaries will not work with an old library. If symbolic link is sufficient, src/lib/compat/compat4x.i386/Makefile or sysinstall should create one. Please do not expect users to do by hand. -- NIIMI Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011226002108.6851B55>