Date: Thu, 8 Oct 1998 06:56:16 -0700 (PDT) From: asami@FreeBSD.ORG (Satoshi Asami) To: cracauer@cons.org Cc: ports@FreeBSD.ORG Subject: Re: Current ports tools prevent libfoo.so.x.y? Message-ID: <199810081356.GAA14536@silvia.hip.berkeley.edu> In-Reply-To: <19981008140448.A3357@cons.org> (message from Martin Cracauer on Thu, 8 Oct 1998 14:04:48 %2B0200)
next in thread | previous in thread | raw e-mail | index | archive | help
* Did anyone mess with the ports tools to prevent us from storing shared * libs with two-level version numbers? Absolutely. We didn't want to confuse our tools. See the ELF guideline (now in handbook's porting section). * I'm doing a port that installs a Linux shared lib with three * symlinks. plist is: * lib/libMesaGL.so.2.6 * lib/libMesaGL.so.2 * lib/libMesaGL.so * lib/libGL.so * * On -current with bsd.port.mk from today and pkg-tools a few days old, * the .6 at the end of the first keeps getting deleted, both in * /var/db/pkg/...CONTENTS and in the package tarfile, makeing packaging * incorrect. So these are linux shared libs? Hmm...I guess you need to add it back manually then. Something like post-install: @echo "lib/libMesaGL.so.2.6" >> ${TMPPLIST} Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810081356.GAA14536>