Having no clear opinion on this, I do have a comment (see below:) Lukas Reichlin wrote: > I think we should group OF packages into different classes as the > long list on > http://octave.sourceforge.net/packages.php is rather confusing. For > example, we could use three classes: > > - main: only about a dozen of packages. The most popular ones, of > general use. High quality. Tested and actively > developed/maintained. What the average user needs, see debian > below. About the packages included in the Matlab student version > > - extra: the less common ones. narrow scope, less tested, under > nconstruction, … > > - legacy: unmaintained, outdated and fragile ones, like the > "symbolic" package. > > > > main packages: (taken from Debian priority packages) > * control > * image > * io > * odepkg > * optim (and its dependencies miscellaneous and struct) > * signal > * statistics
As io is dependent on java, IMO the java pkg should be included in main too. The java pkg is actively maintained and of good quality. And it runs on all platforms with Sun/Oracle Java and OpenJDK, although OpenJDK itself is a bit poorly supported on Windows. <rest snipped> Philip ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
