Date: Thu, 27 May 2004 18:43:09 -0700 From: Eric Anholt <eta@lclark.edu> To: x11@FreeBSD.org Subject: X.Org integration Message-ID: <1085708589.800.13.camel@leguin>
next in thread | raw e-mail | index | archive | help
Well, the modularization isn't going as fast as I had hoped, so what I'm working on is to just make a new xorg-libraries monolithic port of 6.7.0, and probably xorg-clients as well. I'll change xorg-server to depend on xorg-libraries unless some WITH_MODULAR switch is set, and leave the modular libs around (with an informative IGNORE if the switch isn't set) because those ports should be useful some day soon. I'll work on the other monolithic ports as much as I can, but I feel like the others (manpages, print/nest/font/vfbserver, fonts) either don't get used as much or don't require being up to date as seriously as libs, clients, and server do. I want to do them soon, but real life is getting in the way. I'm not sure how to deal with the versioning if we want to support both XFree86-libraries and xorg-libraries (I don't want to, and would love to see XFree86-libraries disappear when xorg-libraries comes around). Are there any concrete arguments to keep XFree86-libraries around if xorg-libraries suits our needs? Note that we'll be installing more shared libraries with xorg-libraries than the old XFree86-libraries port does, so swapping them in and out won't really work. As far as BC issues that came up on IRC recently, here's the deal. Everything in XFree86-libraries should be backwards compatible with XFree86 stuff. The one BC issue in X.Org that's known is that the X.Org server only speaks the new xinerama protocol and not the old one, so it'll work with an X.Org libXinerama but not an XFree86 one. But the X.Org libXinerama should support the XFree86 server fine. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1085708589.800.13.camel>