XFree86 4.4 - an attempt on upgrading ports

[Dejan Lesjak]

On Monday 19 of April 2004 19:32, Joe Marcus Clarke wrote:
> On Mon, 2004-04-19 at 13:23, Tilman Linneweh wrote:
> > Having two bitstream-vera fonts installed is not a good solution.
> > Probably the port is not necessary anymore. But in the past, the
> > distributions with XFree have been out of date often (e.g. fontconfig),
> > so it may be worth to keep them as a seperate port. Maybe the maintainers
> > of bitstream-vera can propose a solution.
>
> It would be best to keep the port, and prevent XF86 from installing its
> own.  This would make it easier to maintain both XF86 and fd.o's X
> server in the tree.

Actually -Server doesn't depend on fonts and neither do -libraries, so there 
shouldn't be a problem with fd.o libraries and server or the X.org server.
I agree however that it's probably better to install bitstream-vera fonts from 
standalone port. I'll try making a patch for this.

> > Are there any other known issues left?

Now that I think about fonts, -Server should probably depend on some font (eg 
fontDefaultBitmaps) as it won't start without at least one.
Another thing is clobbering configuration files (ports/56487 and config file 
lib/X11/xserver/SecurityPolicy listed in pkg-plist of Server, NestServer and 
VirtualFramebufferServer). This can AFAIK be solved by telling xfree build 
system to not clobber them or by installing them as <filename>-sample as is 
probably prefered. I'll see if I can come up with something.
Also apparently the installation of fbdev driver is avoided for i386 and 
sparc, so perhaps it should be done the same for amd64, as well as dummy 
driver which is now avoided for i386 (although I don't see harm in installing 
all the drivers available for particular architecture).
So these are issues that I know of.

Dejan