As we will break some things with the hierarchy with 015 (see the mail about branching) I thought we should go the whole way, so we don't have to break things with later releases. This is to get rid of the /Files directory. It doesn't match anything, is too general and just out of place. Also I know some think that Variable shouldn't be under /System (originally it was basically just tucked away there to make it go somewhere) and I agree. Instead we should have /Data. This will hold runtime data for applications, examples are variable data (/var), service data (/srv) and compile data (/Files/Compile).
I said that we will break things and preferably I'd want just one time breakage, therefor /Data will happen, unless there is a really good argument against or some of the implementations mentioned in the other mail fails. It's all or nothing in my opinion. What's left is to define /Data and here's how I see it: /var -> /Data/Variable: contain varialble data files, and mapping directly against /Data might seem natural I feel that there are better matches for that. /var/lib -> /Data: holds state information per application on the system in named directories. Could be /Data/State as well. /srv -> /Data: service data such as subversion repo, httpd files and mysql database. Could be /Data/Serve as well. /Files/Compile -> /Data/Compile: not much to think of. /Files/ChrootCompile -> /Data/ChrootCompile: same here. The rest of the directories in /Files like Fonts and Codecs will be made into packages, if they aren't already. The only real question is wether /var/lib and /srv should be subdirectories within /Data. -- Jonas _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
