From owner-freebsd-ports Fri Jul 24 11:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03724 for freebsd-ports-outgoing; Fri, 24 Jul 1998 11:31:11 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03718 for ; Fri, 24 Jul 1998 11:31:10 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.HIP.Berkeley.EDU (sji-ca7-188.ix.netcom.com [209.109.235.188]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id LAA13123; Fri, 24 Jul 1998 11:30:46 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id LAA15353; Fri, 24 Jul 1998 11:30:43 -0700 (PDT) Date: Fri, 24 Jul 1998 11:30:43 -0700 (PDT) Message-Id: <199807241830.LAA15353@silvia.HIP.Berkeley.EDU> To: gena@NetVision.net.il CC: ports@FreeBSD.ORG In-reply-to: (message from Gennady Sorokopud on Fri, 24 Jul 1998 10:23:56 +0300 (IDT)) Subject: RE: xforms compatibility From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * The latest version of xfmail (1.3) was developed with xforms-0.88.1, * so there shouldn't be any problem. * * Also 0.88.1 is merely a bug-fix release. Sorry I didn't make myself clear. The problem was was actually reported a few weeks ago with xfmail-1.2 with xforms-0.88.1. But that's not the point. Does the xforms library go through incompatible changes within the same shared library major number? Then, we should do something about it, as there are a lot (16, I think) ports that depend on it. The "something" ranges from making sure everything works fine before xforms is upgraded, to splitting xforms into two ports and changing library basenames (libxforms1, libxforms2, etc.) to allow individual ports to select either one, for instance. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message