(sorry, sent only to sören, it should have gone to everyone!) I have now released a new version of the sockets package and uploaded its html documentation. Some notes, following the manual on http://octave.sourceforge.net/test/developers.html
1) The owner and/or rights on the file area may have been upset by my tries. If there is some clever automatic linking I might have screwed up. Can someone who knows how the file area on /home/frs/project/o/oc/octave/Octave Forge Packages/Individual Package Releases should work check that it looks ok? 2) As Sören pointed out, the generate_html package only runs in octave>3.2. Maybe this can be clarified on the instruction page above. 3) How is the index on http://octave.sourceforge.net/test/packages.php generated? 4) As Carlo (?) pointed out, it feels dangerous when every maintainer have to run rm -rf I think the suggestion of using a low number of "release persons" do the dangerous part and having each package maintainer tag their package might help, although we introduce latency in the chain. 5) Should we keep older versions of packages in the file area on source forge? If so, I think we have to think the structure over has the number of packages is quite big and the number of releases grows with time. It will be tricky to navigate. Should we have a separate "older" directory where one dumps the older releases upon the release of a new one? It seems like the per-package release system works at least partly! Great work! Paul ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
