søn, 04 05 2008 kl. 22:13 +0200, skrev Ólafur Jens Sigurðsson: > On Sun, May 04, 2008 at 09:57:22PM +0200, Søren Hauberg wrote: > > søn, 04 05 2008 kl. 21:55 +0200, skrev Søren Hauberg: > > > søn, 04 05 2008 kl. 21:37 +0200, skrev Ólafur Jens Sigurðsson: > > > > I just saw that the optim version number was not changed during the > > > > last releae of the forge packages. Any specific reason for this or was > > > > it just forgotten? > > > > > > Hmm, I'm a bit confused here. Has the actual contents of the package > > > been changed, while the version number remains the same? I don't think I > > > uploaded a new version of the optim package, because the release tool > > > informed me that the package hadn't changed since the last release. But > > > I might be remembering things wrong... > > > > Ohh, I forgot to mention, that there's a pretty good chance that I > > simply screwed up. I'm pretty good at that ;-) > > :-) > > Well, at least the src/__bfgsmin.cc file had some changes. But you > better double check it ... I am pretty good at screwing up also :-)
Well, this is weird... It seems that the version of 'optim' distributed in the bundle is different from the version distributed as a separate package, although both are at version 1.0.2. I don't really see how this could have happened, so I guess I simply have amazing screwing-up-abilities :-) Any thoughts on what should be done? Should I try to make a 1.0.3 release of this package, and update the bundle as well? Søren ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
