If the decision is still in favor of having a LIB and INCLUDE directory, there will have to be subdirectories under theses for each of the compiler tools, provided the installation can be 'customized'.
This customization, akin to what Ubuntu does, is basically take the package and customize it for the OS, obviously not possible for abandoned commercial-ware apps, like Turbo C and others, but it is possible to customize and repack Pacific C and NASM, so there would be a Pacific C 1.0-freedos.zip that utilizes our full installation 'API' (or toolkit). The problem is then that we as a community would have to repack all open source/public domain software specifically for FreeDOS. This is similar to the approach that Ubuntu uses for their 'approved' packages, they are customized Debian packages for the OS, and while you can still download the non customized version from a debian repository (or compile yourself), they only recommend their custom version for install. Just my two cents....I put on my flame retardant suit, so lets go!!! (LOL) -T ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
