----- Original Message -----
From: "Syl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 15, 2002 4:12 PM
Subject: Re: Tk::JPEG Errors w/Perl 5.6.1 Build 633


> > My view is that you notify Nick Ing-Simmons, because the problem (I
> believe)
> > lies with his code. I don't think it is something that AS should be held
> > accountable for.
> >
> > Nick, in turn, might well say it's your fault for using a Tk::JPEG that
> was
> > compiled for a later version of Tk :-)
>
>
> Why would AS keep/provide a version of Tk::JPEG in its repository that is
> incompatible with the latest build?
> Something does not make sense. Suggestions?
>
>

I'd try and explain it this way:
That version of TK::JPEG that you have installed is quite compatible with Tk
800.023 (afaik - but I haven't checked). But *it* thinks it is incompatible.
It thinks that it's incompatible because it was built on a machine that
contained Tk 800.024 - and because the author has coded it so that (during
compilation) it looks at the current Tk build, grabs the version number,
then insists that that version (or higher) be found whenever it runs.
I think it's unreasonable to expect AS to cover all bases in regard to this.
I suppose they could do it with a little planning and forethought. (They
would just have to ensure that they build their latest version of Tk::JPEG
on a machine that had Tk version 800.023 .... but then those with 800.022 or
lower would still have to upgrade to use it.) I think it would be more
appropriate to ask the author whether it needs to be coded like that - and,
if not, to change it.

The problem's easily fixed, isn't it ? (I realise that it's the
time/frustration spent sorting out this problem which is the major concern.)

And it does seem a little odd that AS have a build of Tk 800.024 but have
not released a ppm for it.

This is the only module I know of where this problem arises. Normally, I
assume, if there's a dependency, then the lowest suitable version number of
that dependency gets coded in. Don't know why the author has done it this
way.

Also bear in mind that many of the people that use Tk::JPEG will be building
it themselves on their own machine. For them this problem will never arise -
and it may well be that the author (and AS) are completely unaware of this
problem in relation to "ppm". I guess it wouldn't hurt to let *both* know.

Cheers,
Rob

_______________________________________________
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to