Problem with liveupdate (zlib)

[Simon Ruderich]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Emmanuel Hainry wrote:
> Citando Simon Ruderich :
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> Now I checked it with other installed ports. It seems there are some
>> problems with livecheck.
> 
> No, those are not "problems". It is a feature (called defaulting to
> something that makes sense in general but may fail).

Oh, sorry. Then I have overreacted a bit. But I couldn't find any
information on how this works. Thanks for your answer.

>> "port livecheck installed" returns this:
>>
>> apr seems to have been updated (port version: 1.2.9, new version: 1.2.8)
>> Error: cannot check if apr-util was updated (regex didn't match)
>> clearsilver seems to have been updated (port version: 0.10.4, new
>> version: 0.10.2)
>> Error: cannot check if db44 was updated (regex didn't match)
>> Error: cannot check if gettext was updated (regex didn't match)
>> Error: cannot check if libxml2 was updated (regex didn't match)
>> Error: cannot check if libxslt was updated (regex didn't match)
>> Error: cannot check if nano was updated (regex didn't match)
>> Error: cannot check if ncurses was updated (regex didn't match)
>> Error: cannot check if ncursesw was updated (regex didn't match)
>> pcre seems to have been updated (port version: 7.1, new version: 7.2)
>> Error: cannot check if perl5.8 was updated (regex didn't match)
>> Error: cannot check if popt was updated (regex didn't match)
>> Error: cannot check if readline was updated (regex didn't match)
> 
> 1) Error: cannot check if apr-util was updated (regex didn't match)
> 
> is the message you get for ports that have not any livecheck
> configuration and for which the default does not work (the default being
> fetching on freshmeat I believe) either because the project is not
> declared on the default site either it has another name.

Oh ok, then the Portfile should be fixed. This would remove this problem.

> 2) pcre seems to have been updated (port version: 7.1, new version: 7.2)
> 
> That's a good message indicating that pcre may need to be updated...
> 
> 3) apr seems to have been updated (port version: 1.2.9, new version:
> 1.2.8)
> 
> This happens if freshmeat has a project declared for this name but the
> page is not as up-to-date as the port. The problem is upstream
> (developper) does not change the project info on freshmeat at every
> release, blame them. 
> Or the port maintainer may try to configure livecheck for it to fetch
> version on an up-to-date site. But since this feature is mostly useful
> for the port-maintainer, he may not need this to know when a port needs
> upgrading.

Ok, thanks for the info. Maybe "port livecheck" should check if the
release number of the homepage is greater then the one in the Portfile
and only then print a "needs update" message. What do you think?

> Emmanuel

Thanks for your answers, but I have still two questions.

"The aim of livecheck is to give the maintainers a quick information if
the Portfile needs an update."
Is this statement correct?

What is with the other "regex didn't match" messages for Portfiles which
have a correct specification of the liveupdate. Is this a limitation of
the regex or am I missing something (again).

Thanks for your help,
Simon
- --
+ privacy is necessary
+ using http://gnupg.org
+ public key id: 0x6115F804EFB33229
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFGlS1dYRX4BO+zMikRCtd2AJ44QymM5hcaqojCy1UwbdVL8z+P/QCcCUtQ
Ks/+o0/OGb0RxtAO+ZtE2B8=
=GkA/
-----END PGP SIGNATURE-----