On Mon, 14 Jan 2008, Shigio YAMAGUCHI wrote:
Maybe you don't want to follow links that go out of the source tree (eg.
/usr/include or whatever), but then you have to check every path component
(boring but possible).
It is likely.
But if user want to do so, it should be accepted.
But worse, symlinks can create loops:
$ ln -s .. foo
Right. Maybe we can do nothing but believe that the user
wants to do something meaningful. :)
In other words: garbage in, garbage out, right? ;)
Well, here is my user point of view: most of the time I use global on an
already existing source tree (I often work in open source software
integration in my day job, and global helped me a LOT), with a layout
intended for eg. the build system, and not for global. So, for me, it is
best if I don't have to "fix" the tree because it confuses global (eg.
dangling symlinks seemed to be a problem). But as of today, I can live
with global as it is. :)
--
[EMAIL PROTECTED]
_______________________________________________
Bug-global mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-global
