[GRASS-dev] r57291: configure.in: disable pwd -W (WinGRASS)

Hi,

re r57291, it's not safe to modify core files after the last RC :frowning:

http://trac.osgeo.org/grass/changeset/57291/grass/branches/releasebranch_6_4/configure.in

There's a missing " quote at the end of line 110. One thousand times lucky this was in a commented out part!!

Hamish

ps- curly brackets do not work for quoting strings or paths, only variable names. if used when not actually needed it fools students of the code into thinking that they will be safe to use instead of real "quotes", and so the misconception & breakage gets propagated on and on. This is especially important for things touching MS Windows where spaces in the path names are common and the future reader may not be a veteran Bourne coder.

Hi,

2013/7/28 Hamish <hamish_b@yahoo.com>:

re r57291, it's not safe to modify core files after the last RC :frowning:

http://trac.osgeo.org/grass/changeset/57291/grass/branches/releasebranch_6_4/configure.in

it has some background, I spent some days with creating a new
up-to-date OSGEO4W packages for produce environment (`msys`) and
building environment (`mingw`). Disabling `pwd -W` turned to
reasonable even before releasing. When spending time on that and other
fucking Windows issues I took liberty to comment it at least.

There's a missing " quote at the end of line 110. One thousand times lucky this was in a commented out part!!

OK, Markus already fixed it. Anyway harmless(!!!)

Martin

2013/7/28 Hamish <hamish_b@yahoo.com>:

re r57291, it's not safe to modify core files after the last RC :frowning:

but sure, you are right. It was not a good idea. Martin

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

Hamish:

re r57291, it's not safe to modify core files after the last RC :frowning:

Martin:

but sure, you are right. It was not a good idea.

but seems no harm done :slight_smile:

It's an interesting conflict -- on one side if we know a fix we wouldn't want
to release without it, on the other side is the law of unintended consequences
resetting the testing clock to zero after any change.

Then add to that taking good advantage of the focused productivity of everyone
pushing to get the release out the door while at the same time not wanting
to raise any dust into the air just prior to release.

it's a delicate balance..

best,
Hamish

Martin Landa wrote:

When spending time on that and other
fucking Windows issues

thanks a lot for your attempt to tame the beast!!

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/r57291-configure-in-disable-pwd-W-WinGRASS-tp5069162p5069229.html
Sent from the Grass - Dev mailing list archive at Nabble.com.