could never work out the syntax for that.
here's the Help on PropGet:
propget (pget, pg): Print the value of a property on files, dirs, or revisions.
usage: 1. propget PROPNAME [TARGET[@REV]...]
2. propget PROPNAME --revprop -r REV [TARGET]
1. Prints versioned props. If specified, REV determines in which
revision the target is first looked up.
2. Prints unversioned remote prop on repos revision.
TARGET only determines which repository to access.
By default, this subcommand will add an extra newline to the end
of the property values so that the output looks pretty. Also,
whenever there are multiple paths involved, each property value
is prefixed with the path with which it is associated. Use
the --strict option to disable these beautifications (useful,
for example, when redirecting binary property values to a file).
Valid options:
-R [--recursive] : descend recursively
-r [--revision] arg : ARG (some commands also take ARG1:ARG2 range)
A revision argument can be one of:
NUMBER revision number
'{' DATE '}' revision at start of the date
'HEAD' latest in repository
'BASE' base rev of item's working copy
'COMMITTED' last commit at or before BASE
'PREV' revision just before COMMITTED
--revprop : operate on a revision property (use with -r)
--strict : use strict semantics
--username arg : specify a username ARG
--password arg : specify a password ARG
--no-auth-cache : do not cache authentication tokens
--non-interactive : do no interactive prompting
--config-dir arg : read user configuration files from directory ARG
My method works, so I am pleased with it. I added a fork to my script to check to see if a new build is neccessary, that was fun