[1155] in SIPB_Linux_Development
Re: minor cleanup
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Nov 8 16:36:58 1995
To: Erik Nygren <nygren@MIT.EDU>
Cc: linux-dev@MIT.EDU
In-Reply-To: Your message of "Wed, 08 Nov 1995 14:18:43 EST."
<199511081918.OAA10251@foundation.mit.edu>
Date: Wed, 08 Nov 1995 16:36:10 EST
From: Greg Hudson <ghudson@MIT.EDU>
> At some point, GCC, afskern, kernel, gif, libc-4.6.27, limekiller,
> pkg-lists, and report should probably get moved into about two
> subdirs but I can't think of good names for them.
Some pointers:
When organizing a directory hierarchy, think first about the meanings
of the top-level directory names, rather than names of contents.
GCC --> system/GCC
afskern & kernel --> system/kernel
gif --> etc/images
libc-4.6.27 --> system/compatlib
limekiller --> somewhere
pkg-lists --> etc/pkglists
report --> etc/report
For example, what is the meaning of "etc"? In a Unix filesystem, etc
contains configuration files. With the data you've given, I can only
guess at what you have in mind for "etc", but it's certainly not
consistent with Unix filesystems.
A good first step in categorizing things is:
dev: Material intended for developers only
This would include "backups", "bugs", "build", "limekiller", "people",
"pkg-lists", as well as any directories containing unfinished products
(probably including "report", "install") and a few others. A nice
advantage of the "dev" category is that the "dev" directory doesn't
have to be very organized, since users don't have to navigate it.
(Yes, "dev" also has a very different meaning in a Unix filesystem,
but people can easily figure out when "dev" means "devices" and when
it means "development" from context. By contrast, "etc" stands only
for "etcetera" which gives no information.)
Beyond that, some things can be moved under "docs" and you can come up
with other categories.
