Hi!
I want to point out a potential issue with the fine-grained approach in
conjunction with using a shared `(ported ...)' namespace, namely the
loss of `easy-installability', by which I mean just checking out the
source code into your (say) $IKARUS_LIBRARY_PATH, and have it work out
of the box:
Imagine having `irregex' and `fmt' maintained in different repositories
(which is the right thing to do, IMO). Now we probably want to have
these library names:
(ported irregex)
(ported fmt)
>From that follows that files from both repositories have to end up in
the same directory, which is not possible by "just checking out".
I don't care much about this issue, since I have created a tool ("doro
symlink-bundle", part of dorodango) which creates appropriate symlinks
using the packaging information, but I wanted to mention the issue
nevertheless, as others may care more about this than myself.
I'd welcome comments of wether this is a real problem for people, or if
they'd be OK with having to install dorodango and run it from time to
time to (re-)populate their $IKARUS_LIBRARY_PATH. Note that the
symlinking is intended just for development, during "normal operation"
dorodango will not use symlinks, but install (copy) the files.
Regards, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
