Ralf Hautkappe wrote: > > Am Mittwoch, 18. Januar 2006 16:16 schrieb Anton Ertl: > > > Maybe you would want to write this stuff. > lol.... caught.. i have got a time problem too ;).... but i think i can > manage > this.... is a latex source okay? (only a include file with chapter section > and so on...)
Texinfo (similar to LaTeX) is preferred. The best would be a "diff -u" from the file gforth.ds. > > For distribution you could just make it a tar-ball, with a Makefile > > that has an "install" target, and leave it to the users to install it, > > and eventually to the distributors to package it up for their > > installation. > i am working on it... but due to lack of knowledge it is takes time.... one > problem is where to put the forth source files in /usr/bin ? or somewhere > below gforth/ or a completly other path? If the Forth source files are executable and to be called by the user, you should put them in $prefix/bin; if you go the shell script route, put the shell scripts there and the Forth source files elsewhere ($prefix/share/$package/$version might be a good directory). Take a look at how other packages are done. Reading the GNU Coding standards <http://www.gnu.org/prep/standards/standards.html> may be helpful, for your case in particular <http://www.gnu.org/prep/standards/standards.html#Managing-Releases>. - anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
