Skip to content
Prev 28629 / 63468 Next

non-digits in svnversion output mess up windows build if (PR#11341)

On Tue, 29 Apr 2008, Duncan Murdoch wrote:

            
It does have that effect, but the error messages
are pretty obscure:
    c:\Rtools\MinGW\bin\windres.exe: rcico.rc:9: syntax error
and
    Error on line 12 in
    e:\R\R-svn\r-devel\src\gnuwin32\installer\R.iss: Value of [Setup]
    section directive "VersionInfoVersion" is invalid.

Both problems are Windows-specific and the desire to not distribute
versions with unintentional uncommitted uncommitted changes is not
Windows-specific.

Note that the rcico.rc problem arises as the first step of compiling R
on Windows from clean source tree, so you cannot even test a proposed
change.  I ran into it because I had to change src/gnuwin32/MkRules to
say that I put Inno Setup in its standard place, "C:/Program Files/Inno
Setup 5", and not in "C:/packages/inno".

I guess I don't need to have USE_SVNVERSION=yes, but doing that means
that version$"svn rev" shows me I have a non-standard version:  that
will show the svn version as something like "123M" or "123:145S".  It
is too bad it only is available on the Windows build.  I think it would
be a good thing to have on the non-Windows builds also.  They use 'svn
info' instead, which does not tell you that the local version is not
the standard one.

If we did that on all platforms then we could check the disribution by
checking that !is.na(as.integer(svn$"svn rev")).

It might also be nice to include the output of 'svn diff' in the
distribution so a user or tester could see how this version was
different than the official one.
----------------------------------------------------------------------------
Bill Dunlap
Insightful Corporation
bill at insightful dot com
360-428-8146

 "All statements in this message represent the opinions of the author and do
 not necessarily reflect Insightful Corporation policy or position."