.. > > DOS - all exe/com/sys files > DOS\APPINFO - lsm files > DOS\DOC\project - documentation for 'project' > DOS\HELP - all help files > DOS\NLS - national language support files > DOS\SOURCE\project - source code for 'project' > > >Note that the install dir from the install program would need to use >C:\DOS as the destdir, and the FreeDOS packages in the next distribution >would not use a 'BIN' directory - the exe/com/sys files would be at the >'root' of the .zip file. So this isn't a huge change. > >Sound okay to everyone? > >If you don't like this, then install your copy of FreeDOS in C:\FDOS >instead of DOS, and the only thing that will be different for you is >that you won't have a C:\FDOS\BIN. > ..
Ok, so we will change the default suggestion to C:\DOS but I would rather we keep the BIN subdirectory. It makes for a cleaner (easier to traverse and see what's there) installation to me. If a user wants, he can always move any programs that he wants out of BIN. From a normal use standpoint, I still don't see any difference other than the PATH tacts on a BIN component, but from a what is installed, and what can I run/what will give me information, it makes a big difference (at least to me). While minor, we will have to update one or so programs to look in HELP instead of ..\HELP for files, or any other behaviour that is expecting to be in BIN. Actual changing of packages to remove BIN should be easy enough with a batch file. Note: the SOURCE\<PROJECT> hierarchy and source packages will soon disapear in favor of a separate single source archive per set. Jeremy ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
