[deimos] [tutorial] [rfc] How to set up a git repository to simplify keeping bindings up to date

[Dejan Lekic]

It is not uncommon that a certain project generates several libraries.
Example: ncurses (libcurses, libpanel, libforms)

I propose each library has a one-to-one correspondent D module inside the 
deimos package. All D modules that correspond to C/C++ header files with the 
same name should reside in subdirectories.

So, say we use ncurses for an example. We whould have:

# "library" modules
/deimos/ncurses.d # -lncurses
/deimos/panel.d   # -lpanel
/deimos/form.d    # -lform
/deimos/menu.d    # -lmenu
# these are made by /usr/include/ncurses/*.h --> .d transformation
/deimos/ncurses/cursesapp.d
/deimos/ncurses/curses.d
/deimos/ncurses/cursesp.d
/deimos/ncurses/cursslk.d
/deimos/ncurses/etip.d
/deimos/ncurses/menu.d
/deimos/ncurses/ncurses_dll.d
/deimos/ncurses/panel.d
/deimos/ncurses/term_entry.d
/deimos/ncurses/tic.d
/deimos/ncurses/cursesf.d
/deimos/ncurses/cursesm.d
/deimos/ncurses/cursesw.d
/deimos/ncurses/eti.d
/deimos/ncurses/form.d
/deimos/ncurses/nc_tparm.d
/deimos/ncurses/ncurses.d
/deimos/ncurses/termcap.d
/deimos/ncurses/term.d
/deimos/ncurses/unctrl.d

Another thing to consider is the fact that if I make such hierarchy in my 
project, I will have to SYMLINK ncurses directory into my deimos/ncurses 
folder, and also have to symlink all "library" D modules...

dmd.conf should contain -I$HOME/include/d/deimos by default. :)