symlink script and proto module questions

[Kevin E Martin]

Soren Sandmann wrote the initial symlink script as described in the
"Transitioning from monolithic to modular" section of the proposal:

    http://wiki.x.org/wiki/ModularizationProposal#transition

I've attached the current version below.  It's not yet complete, but we
can fill in the links as we go.  I've updated it to create the symlinks
for all of the proto module components and an example component in the
lib module.  It's very simple and should be easy to understand, use and
update.

To use the script, run it as follows:

    ./symlink.sh <src-dir> <dst-dir>

where <src-dir> is your monolithic source tree (e.g., /usr/src/xorg/xc)
and <dst-dir> is your modular source tree.  However, since we have not
created the modules and component directory hierarchies yet, you'll need
to create the dirs that the script complains do not exist if you want to
test the script today.


While updating the script, I came up with the following questions:

1. I put all of the headers for libXext in a single dir as was done in
   the xlibs modularization effort.  Should the protocol headers for
   each of the extensions in libXext be put into separate components
   instead?

   Proposed answer: No.

2. The following files are not used anywhere in the tree.  Should they
   still be included in the modular tree?

     xc/include/ap_keysym.h
     xc/include/HPkeysym.h

   Proposed answer: This ultimately depends on if we or the ArchWG think
   that any external programs might use them.  We can include them until
   a final decision is made.

3. The following files are _only_ used in the server.  Should we move
   them to the xserver module (when we create it) or should we leave
   them in the proto module?

     xc/include/XF86keysym.h
     xc/include/extensions/xtrapddmi.h
     xc/include/extensions/xtrapproto.h
     xc/include/extensions/Xagsrv.h

   Proposed answer: Move them to the xserver module, except for
   XF86keysym.h, which should remain with the other keysym files in the
   proto module.

4. The following files are _not_ used in the server.  Should we move
   them to the lib module (when we create it) or should we leave
   them in the proto module?

     xc/include/Xthreads.h
     xc/include/extensions/Xinerama.h
     xc/include/extensions/XRes.h
     xc/include/extensions/scrnsaver.h
     xc/include/extensions/xtrapemacros.h
     xc/include/extensions/xtraplib.h
     xc/include/extensions/xtraplibp.h
     xc/include/extensions/vldXvMC.h
     xc/include/extensions/Xvlib.h
     xc/include/extensions/XvMClib.h
     xc/include/extensions/lbxbuf.h
     xc/include/extensions/lbxbufstr.h
     xc/include/extensions/Xdbe.h
     xc/include/fonts/FS.h
     xc/include/fonts/FSproto.h
     xc/include/GL/glu.h

   Proposed answer: Move them to the lib module.

5. Are there other headers listed in the symlink.sh script that should
   be moved to the xserver or lib module?

Once we answer these questions, the next step is to create the proto
module and the component dirs.  Then, we can open up the tree to start
creating the other modules.

Thanks,
Kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: symlink.sh
Type: application/x-sh
Size: 10626 bytes
Desc: not available
Url : http://lists.x.org/archives/xorg-modular/attachments/20050429/300739a8/symlink.sh