Hi Bonnie, > what is involved in putting updated packages into zip format? > i have a dos zip program on my freedos boot. > how could i help?
Please contact Geraldo: geraldonetto xy gmail.com (xy = @sign) Check the software list: www.freedos.org/freedos/software/ Things updated after ca 9/2008 were not part of FreeDOS 1.0, so to make them part of 1.1, we need a zip in the right style which can be used by the installer, fdpkg and fdupdate... The fdupdate repository: www.viste-family.net/mateusz/fdupdate/ ...contains zips in the right style, but often without source. Some of them are not for programs which will be in 1.1, others are older than 9/2008, but in general, the repository tells you which 1.1 updates-newer-than-1.0 we already have zipped up... Here are 2 1/2 examples: DEBUG 1.13 and EDIT 0.9a in their "zip on normal download page" shape. DEBUG is not suitable for the installer, but EDIT almost ;-). The trick is to put all files in the right directories and add a LSM file. See the LSMs of any package for examples for LSM file contents. Debug 1.13: zipinfo -1 debug113.zip ... readme.txt debug.asm debug.com debugx.com instr.set instr.key instr.ord debugtbl.inc mktables.c make.bat makec.bat samples/ samples/make.bat samples/dpmicl32.com samples/dpmicl32.asm samples/dpmicl16.asm samples/dpmicl16.com debug.txt fptostr.inc debxxvdd.dll As you see, everything is in the main directory and a samples subdirectory. This zip is meant to be unzipped in a directory specially made for debug, so it is not useable by the installer. Edit 0.9 comes in 2 separate zips: zipinfo -1 edit09ax.zip ... bin/ bin/edit.exe bin/edit.hlp doc/ doc/bugs.txt doc/contrib.txt doc/copying doc/edit.lsm As you see here, the files needed to run EDIT are all in bin/ and the documenation is in doc/ but there is no LSM file and the documentation SHOULD be in doc/edit/ instead of in doc/. zipinfo -1 edit09as.zip ... doc/ doc/edit/ doc/edit/bugs.txt doc/edit/contrib.txt doc/edit/copying doc/edit/edit.lsm source/ source/edit/ source/edit/asciitab.c source/edit/build_ed.bat source/edit/calendar.c source/edit/config.c source/edit/config.h source/edit/edit.c source/edit/edit.h source/edit/edit.mak source/edit/edit.txt source/edit/menus.c This zip is even better: the sources are in source/edit and the docs are in doc/edit and there is a LSM file already :-). It is not PERFECT, though, beccause the LSM file should not be in the doc/edit/ directory but in appinfo/ ;-). Note that both the "binary" and the "source" directory contain the documentation. What you would do to help with FreeDOS 1.1, you would move the LSM file in edit09as.zip, move the docs in edit09ax.zip and add a LSM to it. For debug113.zip, you would put all the contents into suitable subdirectories. In this example, I would put the "samples" into source/debug/samples/. Then you would sent those files to Mateusz and/or Jim so they can be added to the fdupdate repository and the collection of files for the FreeDOS 1.1 cdrom :-). You can either put both source and binaries in one zip or make 2 separate zips, as it is easy to "split up" into two zips in automated way later ;-) HOWEVER, this is only an example! It is quite possible that somebody else already made installable DEBUG and EDIT zip files. This is why you ask Geraldo and maybe Mateusz first. Most of the BASE category is probably already done. Thanks for helping :-) Eric PS: The idea of the directory structure is that after you unzip every zip in c:/freedos/ or c:/fdos/ or similar, ALL programs will be in c:/freedos/bin and all the docs and source code will be in c:/freedos/doc/NAME-OF-PROGRAM/ and c:/freedos/source/NAME-OF-PROGRAM/ respectively and that c:/freedos/appinfo/ has one NAME-OF-PROGRAM.LSM file for each program you have installed :-)). PPS: If there are NAME-OF-PROGRAM.es or other *.LANGUAGE files, they go in the NLS/ directory, and if some program needs many files to run (e.g. OpenWatcom), they can go in their own separate subdirectory instead of into BIN/ ... ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
