livecheck behaviour
Ryan Schmidt
ryandesign at macports.org
Tue Nov 19 09:31:45 PST 2013
On Nov 19, 2013, at 07:15, John Patrick wrote:
> Josh, does that also cover the potential mirror not sync'ing fast enough issue, or does livecheck always go to the master mirror? Or should livecheck always go to the master mirror?
There are defaults for the livecheck.type, livecheck.url, livecheck.regex, which can vary based on the master_sites value (e.g. setting “master_sites googlecode” sets up livecheck for Google Code as well) or be changed by a portgroup. If they’re not suitable for a particular port, you can and should change them.
Livecheck can currently only check a single URL, and match a single regular expression across its contents, and return to you the maximum version number it found. This has served us well in most cases so far.
More information about the macports-dev
mailing list