From owner-freebsd-current Tue May 16 11:49: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ucsu.Colorado.EDU (ucsu.Colorado.EDU [128.138.129.83]) by hub.freebsd.org (Postfix) with ESMTP id B223B37B97A for ; Tue, 16 May 2000 11:48:42 -0700 (PDT) (envelope-from vinson@ucsu.Colorado.EDU) Received: from localhost (vinson@localhost) by ucsu.Colorado.EDU (8.9.3/8.9.3/ITS-5.0/standard) with SMTP id MAA18645 for ; Tue, 16 May 2000 12:48:41 -0600 (MDT) Date: Tue, 16 May 2000 12:48:41 -0600 (MDT) From: VINSON WAYNE HOWARD To: freebsd-current@freebsd.org Subject: Re: Motif is now Open Source 8) In-Reply-To: <200005161744.LAA15207@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, I'm saying that OpenSource Motif *will* be going through lots of > gyrations in the future, and these gyrations may cause instabilities in > the JDK. > > But, if the JDK uses the Motif version it was compiled against, it will > work 'consistently. > > Unlike X (which rarely changes), I suspect the Motif stuff to change > alot. > > > Nate IT seems to me that this might not be much of a problem. Have a "last stable motif" port/package. The JDK guys can choose when to move it to a new version, and should do so when they see a version that doen't cause problems for the JDK. Don't give this port/package the normal motif library names, but sim-link it to those names. Compile the JDK against the special lib names, not the normal motif names. Now, have a "bleeding edge" motif that can be installed. it installs into the normal motif locations. look what this does for the user: 1. If they'd rather be stable anyways, they just install the last-good version. all is well - both the jdk and their other apps see an acceptable motif. 2. If they need bleeding-edge, they can install it. JDK will still work. Yes, they have two motif versions, but they need both versions, so this is OK. 3. If they start out last-good, and move to bleeding edge, everything works out just fine. 4. If a bleeding-edge user updates their last-good motif, it doesn't screw things up since last-good can't sim-link over the real libs. Just the JDK is affected. 5. If a user doesn't use the jdk, they can install bleeding-edge and it works for all non-JDK apps. One usefull addon would be to have bleeding-edge re-create the last-good sim-links when it is pkg_deleted if that's possible. Just my $0.02 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message