On Thursday 10 May 2007 11:28, Dirk Stoecker wrote:
You're right, but - That's a tools problem only. The user wont see it, wheras the users sees the project names and structures.
If you see it as a tools problem, than it doesn't make much difference, if it's a ':' or a '/' as it's up to the user interface how to present that.
- It's the same for Unix filesystems. You also do not know if /foo/bar is a directory or a file. So in this sense it is consistent.
It might be consistent with filesystems, but it would add complexity to implementations and the API. So I'm not sure that consistency is really beneficial.
The Unix filesystem seperation is widely used, accepted and understood (including it's limitations). I think it's better to use it than redoing it using ":". I also used adapted naming schemes for some of my projects and finally came to conclusion, that Unix file system or URL type addressing would have been better (but it's to late to change). I think for Buildsystem it is still time to change.
As the ':' has some drawbacks it would be nice to have a better solution (and a change might be a bit painful, but not impossible). But the '/' has drawbacks as well. So does somebody have an idea which comes with less drawbacks? -- Cornelius Schumacher <cschum@suse.de> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org