'pngread' and 'jpgread' usage?

[Søren Hauberg]

tir, 09 06 2009 kl. 10:51 +0200, skrev Primoz PETERLIN:
> You should explain right from the start that you just want the
> dependence on libpng and libjpeg be somebody else's concern, and
> people would understand. :)

:-)

> Seriously, since imread and imwrite are part of the octave proper, I
> think it is an unnecessary duplication of efforts to keep supporting
> them in their present form. However, in order not to break somebody's
> existing scripts, I suggest for the interrim period replacing them
> with .m scripts calling imread/imwrite, and marking their use as
> deprecated in the documentation.

Yeah, I guess that's how I'll actually do it.

> This still breaks things for people using an old version of octave
> along with the newest version of image package. I am not familiar
> enough with the octave packaging system - does it provide a "require"
> statement (one needs at least the version where imread/imwrite are
> part of octave)?

You can indeed require specific versions of Octave. The latest release
of the 'image' package requires Octave 3.1.55 which was a development
snapshot of 3.2. 

Søren