livecheck behaviour

[Joshua Root]

On 2013-11-19 23:50 , Peter Danecek wrote:
> 
> Hi all,
> I am just experimenting a bit with livecheck, and wonder if the behaviour below is really the desired behaviour. 
> 
> --- snip ---
> DEBUG: Port (livecheck) version is 0.8.5
> DEBUG: Fetching https://pypi.python.org/packages/source/o/obspy/
> DEBUG: The regex is ">obspy-(\d+\.\d+\.\d+)\.zip<"
> DEBUG: The regex matched ">obspy-0.8.0.zip<", extracted "0.8.0"
> DEBUG: The regex matched ">obspy-0.8.3.zip<", extracted "0.8.3"
> DEBUG: The regex matched ">obspy-0.8.4.zip<", extracted "0.8.4"
> py-obspy seems to have been updated (port version: 0.8.5, new version: 0.8.4)
> --- snip ---
> 
> I would argue 0.8.5 > 0.8.4 so ideally this situation would be recognised. Is there some way to influence the evaluation, e.g. to result "seems to be up to date" in such a case. 
> 
> 
> NOTE: In this case this actually is not really needed (it was only a test). But I am looking at some other situation. Where `updates` got into a different directory. So in that case a somewhat different behaviour would be helpful.
> 
> It would also be interesting to check for the presence of some regex, in case it is not to judge that the port is up-to-date. Would this be possible somehow?

This behaviour is intentional since not finding the current version
means you need to fix your livecheck. The wording of the message could
be different in that case but it should not say "seems to be up to date".

- Josh