Image package
Thomas Treichl
Thomas.Treichl at gmx.net
Tue Dec 9 02:42:31 CST 2008
Søren Hauberg schrieb:
> tir, 09 12 2008 kl. 09:16 +0100, skrev Thomas Treichl:
>> Bob told me, that -after another trial- he was able to install my modified
>> image-1.0.8.tar.gz package with Octave.app 3.0.3, too. Is there any reason why
>> we should *not* change the Makefile of the image package like I suggested
>> before? Can I commit that changes?
>
> Well, actually, the 'imread' and 'imwrite' functions are no longer
> available in octave-forge SVN as they have now been moved to core
> Octave. The problem is that the current release process in Octave-Forge
> is fairly broken, meaning that it's quite a bit of work to actually make
> a new release, so currently no Octave-Forge release is planned before
> Octave 3.2 is released. I plan on improving the release process, but I'm
> waiting for some patches to core Octave to be reviewed.
>
> That being said, if there is a strong wish to have a new release of
> Octave-Forge, please bring it up on the Octave-Forge mailing list.
Well, I would say that it is not necessary to create a new release now, thanks.
But then I must ask the other way: Let's say after 3.2.0, will there be portions
of an image package available at Octave-Forge left that link against ImageMagick?
Nevertheless, I think changing the file is no fault before it is forgotten, what
would you say?
Thomas
More information about the Help-octave
mailing list