Index: docs/dev/fhs.pod =================================================================== --- docs/dev/fhs.pod (revision 10357) +++ docs/dev/fhs.pod (revision 39000) @@ -1,3 +1,6 @@ +# Copyright (C) 2001-2007, Parrot Foundation. +# $Id$ + =pod =head1 Title @@ -2,3 +5,3 @@ -FHS - Filesystem Hieararchy Standard and Parrot +FHS - Filesystem Hierarchy Standard and Parrot @@ -53,7 +56,7 @@ This is the primary directory of executable commands on the system. All executables that are intended to be called directly by the user (i.e. -parrot, pdump, disassemble, parrot-debugger, pbc_info, pbg_merge, ...) +parrot, parrot_debugger, pbc_disassemble, pbc_dump, pbc_info, pbg_merge, ...) should go here. The current version number should be appended to the binaries itself and a symlink needs to be created that points from the binary with version number to the normal name of the file without a @@ -79,7 +82,7 @@ This is libparrot$(SOEXT).$(SOVERSION) if the parrot binary was linked dynamically. Otherwise nothing. -Also Parrot usees a single subdirectory called I to +Also Parrot uses a single subdirectory called I to store all architecture-dependent data exclusively used by parrot. These files are grouped by the parrot version they belong to. So we'll have I, I, etc. @@ -97,7 +100,7 @@ The I hierarchy is for all read-only architecture independent data files. Parrot stores those files in -I. For example all .imc, .pasm and .imc +I. For example all .pasm and .pir files should go there as well as data files for libraries like images and such. @@ -154,10 +157,10 @@ This is also documentation for I. -=item /usr/parrot-config.imc +=item /usr/parrot-config.pir This is a command which can be called from the user. It should be in -I, maybe without the .imc suffix. +I, maybe without the .pir suffix. =back Property changes on: docs/dev/fhs.pod ___________________________________________________________________ Name: svn:eol-style + native Name: svn:keywords + Author Date Id Revision