* David Bateman <[EMAIL PROTECTED]> [2008-04-18 14:54]: > mkdoc and mktexi used to be distributed with the octave-forge monolithic > releases.. They are however not distributed with the packages.. There > are lots of things in the SVN to build windows binaries, mac binaries, > packages, rpms, web pages and documentation that aren't distributed > apart from the SVN. How would you suggest they are distributed?
As a separated package, with a name like octave-forge-dev or octave-forge-utils. The scripts would be installed in, e.g., /usr/bin and this should simplify things for the developers. > The mkdoc and mktexi scripts are only to build fixed.texi and comms.texi > files, though are usable by other octave-forge packages wanting to have > automatic generation of the documentation in the same manner. Why > distribute this at all? If you have to for octave-forge on debian then > package mkdoc and mktexi with a build depends only for the comms and fixed > toolboxes.. Yes, this is the idea. -- Rafael ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
