On Tue, Nov 3, 2009 at 6:59 PM, Joe Emenaker <j...@emenaker.com> wrote: ... > Oh, okay. But what I don't see there is some decision-making policy about > extraneous directories. For example, why does CTMOUSE get its own folder > under /FDOS/BIN/? What criteria must a package meet in order to warrant > special directories? > > Also, same goes for the /FDOS main directory. Looks like there's not a lot > there. BIN/, DOC/, SOURCE/, APPINFO, FDAUTO.BAT... are there any > rules/guidelines aimed at keeping this very tidy, or can packages just throw > random stuff in there? ... > - Joe
The idea is to keep the directory structure simple and organized. Any executable files and needed support files (assuming only a few) should go into the BIN subdirectory - ideally this would be the only directory to add to PATH, however if a particular program includes several support files or utility programs (such as CuteMouse) then it may have its own subdirectory [how the maintainer of a particular package originally packages the files is the basis for which files go where]. Individual packages should refrain from installing files to the main directory (FDOS/) unless it makes sense with the overall distribution such as copies of AUTOEXEC/CONFIG and top level FreeDOS directories. The decision to include files in subdirectories named after the package under the other [non BIN & HELP] directories is somewhat arbitrary but the basic guideline is if there is more than one file or that one file is not named after the package then it should be in a subdirectory named after the package. Jim's original document is what I used as a guide when updating/creating packages, with the APPINFO subdirectory being the only addition for any META information about the packages/programs installed. Others have taken over since I last worked on packaging files but I think the above is still correct. Jeremy ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
