Modularization proposal updated

Kevin E Martin kem at freedesktop.org
Mon Apr 11 14:48:31 PDT 2005


On Mon, Apr 11, 2005 at 11:41:40PM +0200, Roland Mainz wrote:
> Adam Jackson wrote:
> > > > I have updated the modularization proposal as discussed.  The changes
> > > > were to generalize the driver module (as suggested by Keith and myself)
> > > > and explain that the configure options will be both standardized and
> > > > documented (as suggested by Egbert et al.).  The updated proposal can be
> > > > found here:
> > > >
> > > >     http://wiki.x.org/wiki/ModularizationProposal
> > >
> > > Two things:
> > > 1. XRX is still no DDX (it mainly belongs into the app/ module AFAIK)
> > 
> > It's a wiki, you know. ;)
> 
> Yes, but I am not sure whether anyone else except the author is allowed
> to edit it (technicially I can edit it but I would prefer if Kevin would
> do that (since there is no editoral review process for changes in this
> version of Wiki and I don't like to put random nonsense into other
> people's work... :))

I've change it now.

> > > 2. Where should server-specific config files stored (I am mainly
> > > thinking about the whole XpConfig/ hieracy which the print server needs
> > > to start (e.g. it will refuse to start without having those files so
> > > they should be placed close to the server sources IMO)) ?
> > 
> > Config files belong with the app that needs them.
> 
> OK... that would be the xserver module then...

That's a reasonable question.  What should we do with XpConfig,
xorgconfig, etc?  The app to which these belong is the server.

> > Does this mean a combined print+display server will fail to start display
> > graphics if the XpConfig hierarchy is missing?
> 
> If you force to run it in "print" mode then the answer is definately
> "yes" (since you will only have print screens in the "print"-only mode
> and all print drivers will refuse to initalise if the core config data
> are missing). The same applies to the "video+print" mode but that could
> be adjusted to a plain warning and then the Xserver only comes up with
> "video" screens.

I think this is a good reason why the default is currently to build
separate video and print servers.


More information about the xorg-modular mailing list