tir, 23 12 2008 kl. 07:56 -0700, skrev Jonathan Stickel: > On 12/22/08 octave-dev-requ...@lists.sourceforge.net wrote: > > What I suggest is that package maintainers makes the releases. The > > only thing they wont be able to do is to upload the packages and web > > pages to Sourceforge. That is, when a maintainer decides to make a > > release he/she creates the package file, and the relevant web pages. > > These files should then be made available to a privileged user who then > > uploads them to Sourceforge. This is still a bit tedious and could be > > automated, but I don't think it can be improved within the limitations > > of Sourceforge. > > This seems like a good incremental step. So, how do we do it? I > imagine that preparing a release tarball from a package folder is easy > enough, but I wouldn't know where to begin with preparing web pages for > my package.
So, I've created a package that allows you to build web pages for any installed package. It's work in progress, but what I currently have is available at http://hauberg.org/wiki/doku.php?id=generate_html With this package installed you can do something like generate_package_html ("your_package_name", "outdir", "octave-forge"); which will generate a directory with HTML files called "outdir". The "octave-forge" argument affects the visual layout of the generated pages. The HTML files does, however, not integrate with the current function reference at octave.sf.net. So, some work is needed before this stuff can be used... Søren ------------------------------------------------------------------------------ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
