[GRASS-dev] [GRASS GIS] #1950: wingrass: replace rxvt with conhost.exe

[GRASS GIS]

#1950: wingrass: replace rxvt with conhost.exe
-----------------------+----------------------------------------------------
 Reporter:  hamish     |       Owner:  grass-dev@…              
     Type:  task       |      Status:  new                      
 Priority:  major      |   Milestone:  6.4.3                    
Component:  Packaging  |     Version:  svn-develbranch6         
 Keywords:  wingrass   |    Platform:  MSWindows 7              
      Cpu:  All        |  
-----------------------+----------------------------------------------------
Changes (by mmetz):

  * milestone:  6.4.4 => 6.4.3


Comment:

 Replying to [comment:8 hamish]:
 > Replying to [comment:7 mmetz]:
 > > The only fuss I see is about keeping rxvt.
 >
 > I don't care about keeping rxvt. I have no problem with replacing it if
 it's for the best. What I care about is last minute untested [in 6.x]
 changes in the release branch,

 It was you how broke translation for 16 languages in the last minute. I do
 not expect to be GRASS 6.4.3rc4 to be released in the next minute.

 > and keeping the development team a nice community to participate in.

 ?

 IMHO, what counts is releasing a stable version. Soon. You prevent this.
 This is, i.e you are, not nice.

 >
 > > In rxvt, copy+paste never worked for me,
 >
 > I've used it a lot and never had a problem with that, shrug.

 It is safer to use the system's console window.

 >
 > > but since I am sometimes trying to fix bugs for wingrass, I changed
 > > years ago to system console + sh in my local wingrass versions.
 >
 > so you've no experience with the current version and are basing your
 impression on some years old thing?

 Your thing is even older. Please keep the development team a nice
 community and do not post provoking posts.

 I understand, I will immediately update mswindows/osgeo4w/msys.bat to the
 current stable version of msys. Oops, noting to update, stable since 2009.

 >
 > > It seems that using rxvt can be regarded as a bug.
 >
 > the question is if it is a serious enough problem to risk destabilizing
 the one wingrass command line option in 6.x which is 99% working properly,
 shortly before a public release. !@$!#@$

 Stabilizing, not destabilizing.
 >
 > > I updated msys.bat to the official stable version (MSYS 2009)
 > > in r55996,7 for rebr64, devbr6, respectively.
 >
 > thanks for respecting the "just wait a bit" requests of others... great
 collaborative working environment based on mutual respect we have here.

 The request to not use rxvt is rather old.

 Why did you not "just wait a bit" before breaking translations?

 >
 > by the way, you overwrote some local changes to the msys.bat script in
 your commits. (i.e. our "%PART1%" test to see that paths with spaces were
 correctly quoted, see original commit to svn + #905, #629)

 These are not local changes. The part you refer to is not even in
 msys-1.0.11. Can you please provide an example where this test is needed?

 >
 > > About changes and testing: this change is not in a release candidate
 > > and far from being in an official release. A pity.
 >
 > Perhaps, but 6.4.4 doesn't have to be that far away. Shoving core stuff
 in at the last minute is bad bad bad bad, no matter how innocent looking
 it seems. Now we have something else to spend many hours testing, which is
 annoying.

 > have you started that? was your local replacement+testing done for 6.x
 or trunk?

 I spent years testing. In trunk and relbr64. Not in debr6, because there
 is no reason for the existence of devbr6. Please respond in the
 appropriate thread.

 > I'm partly annoyed as we have a number of other major wingrass bugs to
 fix before release, it's hard to get anyone to work on them, and instead
 we seem to be wasting time and energy here discussing the bike shed.

 My .2c:

 downgrade the osgeo4w python and wxpython versions
 upgrade msys and mingw
 fix grass-addons

 >
 >
 > thanks,
 > Hamish

 welcome,

 Markus

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1950#comment:9>
GRASS GIS <http://grass.osgeo.org>