I did not mean to start a flame war.
A discussion is not necessary a flame war :-)
Since there is no *practical* difference between the two directories currently (e.g. both are in the default search path)
BTW: The directory taxonomy at run-time is less important than the directory hierarchy of the source tree. I mean, the directory structure of /app and /srv is flat at run-time and it is perhaps fine that way. And yes, the shell has a default search path which practically merges the two directories at run-time from the user point of view.
But at compile-time, it makes sense to have a slightly more complex hierarchy of source directories, to ease the navigation and orientation in the source tree. In most Linux distributions you also have at least a two-level hierarchy of packages, but once installed, the files (or at least the binaries) end up in a few common directories (which are usually all in the search path).
the interpretation of those directories is, by definition, subjective. The interpretation of /drv, on the other hand, is clear
Well, at least for me and Jakub the interpretation of /srv is as clear as the interpretation of /drv. There are system services in /srv.
Yes, the criterion is not based on purely technical merits and therefore it can be labelled as subjective. But that alone does not make it unreasonable.
It does not. I don't insist on websrv not being in /app and if it bothers you being in /srv I will move it back. I just thought that was a good idea, based on my personal interpretation of /app and /srv. Please, let's not introduce yet another completely arbitrary directory.
OK, another top-level directory is perhaps not an optimal solution. So what about creating subcategories in the uspace/app source tree? The run-time /app directory shall stay flat.
M.D. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
