[csw-maintainers] Is there a reason not to fix uninitialized $REVISION warning

Mon Nov 7 10:19:31 CET 2011

Hi all,

I'm new to OpenCSW and GAR. Can anybody tell me If there is a reason
behind keeping "Use of uninitialized value $REVISION in sprint ..." warning
in mkpackage?

I've cloned GAR into a private mercurial repository to be able track changes 
not accepted in trunk. Mercurial does not expand keywords by default, so
I get warning about uninitialized REVISION on each build. I find it quite
annoying and fixed it in my branch (see attached patch), but I it looks like
the warning is left intentionally. It is well known and mkpackage contains
comment about the warning in the code. Can somebody explain me why?

Thank you,
Andrey
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mkpackage-norev-warning.patch
Type: application/octet-stream
Size: 691 bytes
Desc: mkpackage-norev-warning.patch
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20111107/1dd86e9c/attachment.obj>