Kenneth J. Davis wrote:
Actually, it seems that I spoke too soon. I had always just installed fdbasecd.iso and that gives a very clean C:\FDOS install. Yesterday, I tried the full CD and it throws a *lot* more stuff directly into C:\FDOS and whatnot. The austere elegance of the C:\FDOS directory kinda goes out the window. Ah, well....On Tue, Nov 3, 2009 at 6:59 PM, Joe Emenaker <j...@emenaker.com> wrote: ...... are there any rules/guidelines aimed at keeping this very tidy, or can packages just throw random stuff in there?The idea is to keep the directory structure simple and organized.
Okay, next question: Is there any provision for packaging of apps which aren't part of the FreeDOS distribution, per se (so they wouldn't belong in C:\FDOS)? Suppose, for example, that I wanted to package something like Borland's Turbo C so that I can easily deploy it to an entire computer lab of PC's, say. I doubt that putting it under C:\FDOS is the best place for this, but I've noticed that the packaging guidelines ask that the ZIP file only contain relative paths (intended to be relative to C:\FDOS). So, at first glance, it doesn't seem that the package maintainer has any way of indicating that it belongs outside of C:\FDOS.... like maybe a C:\APPS or a C:\BIN or something.Any executable files and needed support files (assuming only a few) should go into the BIN subdirectory
Well, that's not really what seems to be happening. I look in C:\FDOS\BIN and there's all kinds of odd stuff. *.CPI files, CP*.TBL, META*.BIN, etc.. Is there still hope that all of this will eventually get organized into per-package folders, or is it kind of a lost cause at this point? Incidentally, I have noticed that some packages *do* have all of their files in a dedicated folder and then they just have a .BAT file in C:\FDOS\BIN which redirects to the actual executable(s) in the package folder. Lynx does this, for example. The problem, however, is that the LYNX\ folder is placed directly under C:\FDOS. Is there a suggestion/plan/guideline that dedicated app directories be placed in a special place? Maybe a C:\FDOS\LIB, or a C:\FDOS\APPS, or even under C:\FDOS\BIN? Taking all of Lynx's individual files out of C:\FDOS\BIN and putting them into a new C:\FDOS\LYNX doesn't seem like all that much of an improvement.... 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.
- Joe
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ 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
