And while I usually don't follow up on myself, writing the last mails gave
me an idea.
Lars Duening wrote:
>When tracking an external development independently with your own version
>control system, you have no choice but to dissociate your local version
>numbers from the program's version numbers:
>
> PRCS version upstream-3.2 -> Program version 1.5
> PRCS version upstream-3.3 -> Program version 1.5a
> PRCS version upstream-3.4 -> Program version 1.6-sp3
>
>You'll have to store the program version by some other means, in the PRCS
>log messages, or by using a project keyword like VendorVersion. This of
>course means that working with less-recent versions of the programs always
>require looking up your local version number.
It would be nice if PRCS could select revisions by matching on keywords,
for example:
prcs checkout -k 'VendorVersion="1.6-sp3"'
would checkout the last revision fulfilling the condition, in this case
upstream-3.4 .
Other possible combinations:
prcs info -r upstream-3 -k 'Submitter="jrandom"'
would print the info for all revisions in the upstream-3 branch submitted
by Mr. JRandom.
If you want to get really fancy, you could allow the matching on several
keywords (-k 'Submitter="jrandom",System="Foonly"') which all would have to
match. Anything more complex is better handled by using PRCS from a shell
script.
And speaking of which: it would also be nice if 'prcs info' would allow to
format the output similar to $Format$:
prcs info -f "$ProjectVersion$ $VendorVersion$"
--
Lars Duening; lars@xxxxxxxxxxx
GPG Key: http://www.bearnip.com/lars/lars-duening.gpgkey
|
