Module name == dir hierarchy seems to make devel awkward...

[Rob Browning]

Maybe I'm missing an obvious alternative, but say guile decides to
define in it's new module hierarchy a section like (ui graphical 3-d
fancy) and say I want to create an opengl module, which should
obviously :> be accessed as

  (use-modules (ui graphical 3-d fancy opengl))

With the current module system, it seems like in my development
directory for guile-opengl, if I wanted to work without having to do a
"make install" every time I made a change, I'd have to have a mostly
empty deep subtree for all my files.  i.e. my project's directories
would have to look something like this:

  guile-opengl/INSTALL
  guile-opengl/README
  guile-opengl/Makefile.am
  ...
  guile-opengl/graphical/3-d/fancy/opengl.scm
  guile-opengl/graphical/3-d/fancy/opengl/low-level.scm
  ...

So I'd have three levels of empty subdirectories just to mirror the
eventual install hierarchy.  To me this seems awkward, but I don't see
an alternative given the current module system design.

So is there an alternative, or is this just expected?

Thanks

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930