On 09/04/14 03:17, Vaclav Petras wrote:
On Tue, Apr 8, 2014 at 9:09 PM, Glynn Clements gl...@gclements.plus.com
mailto:gl...@gclements.plus.com wrote:
If there's no Python installed, the installer can install it. If
Python is installed and the version is compatible, the installer can
Agreeing with Moritz,
In other words, there are some types of users (those that don't read
anything provided by the developers) for whom I am sometimes tempted to
just say RTFM instead of trying to find ways to make it possible for them
to still use GRASS
I used to start my GRASS GIS courses by
On Wed, Apr 9, 2014 at 9:21 AM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 09/04/14 03:17, Vaclav Petras wrote:
On Tue, Apr 8, 2014 at 9:09 PM, Glynn Clements gl...@gclements.plus.com
mailto:gl...@gclements.plus.com wrote:
If there's no Python installed, the installer can
On 4/9/14, Yann Chemin yche...@gmail.com wrote:
I used to start my GRASS GIS courses by saying to students that this is not
going to work if you do not read the instructions.
Not sure about this.
Was just teaching GRASS GIS 7.0.0beta1 and it worked pretty well.
I would not 'threaten' them in
One Windows problem is that there is no package manager
who takes the user's hand which is the reason for these large
standalone applications on MS Windows.
[...]
Personally, I am a bit afraid that by going down the first route we
concentrate much developer time that could be spent on other
On 07/04/14 23:13, Glynn Clements wrote:
Moritz Lennert wrote:
In my understanding we were still quite far away from solving the python
on windows issues.
That depends upon what you consider the issue to be.
If the user already has a compatible version of Python and the
required libraries
On Tue, Apr 8, 2014 at 9:09 PM, Glynn Clements gl...@gclements.plus.comwrote:
If there's no Python installed, the installer can install it. If
Python is installed and the version is compatible, the installer can
install any required packages. Otherwise, it can at least inform the
user of the
On 06/04/14 15:25, Martin Landa wrote:
Hi,
2014-04-06 15:16 GMT+02:00 Moritz Lennert mlenn...@club.worldonline.be:
As already mentioned I was also a bit surprised by this. I'm not sure we are
really ready for something more than a tech-preview (and not a real
release), but maybe it could be
On 07/04/14 00:19, Helena Mitasova wrote:
I believe that we have a communication problem here rather than a disagreement
about the GRASS6.5:
Hamish says:
GRASS 6.x is already far along into bugfix maintenance mode.
*Please, just leave it to naturally and quietly make its way into history.*
I
On 07/04/14 11:22, Moritz Lennert wrote:
On 06/04/14 15:25, Martin Landa wrote:
Hi,
2014-04-06 15:16 GMT+02:00 Moritz Lennert mlenn...@club.worldonline.be:
As already mentioned I was also a bit surprised by this. I'm not sure
we are
really ready for something more than a tech-preview (and
As goes for encoding issues - I would like to see one change made for
attribute data handling. As correct encoding needs to be used in quite
many places (Python 3; multiple output formats as OGR ESRI Shapefile;
KML etc.), I would propose to add data encoding to the database
connection
On Mon, Apr 7, 2014 at 12:19 AM, Helena Mitasova hmit...@ncsu.edu wrote:
I believe that we have a communication problem here rather than a
disagreement about the GRASS6.5:
Hamish says:
GRASS 6.x is already far along into bugfix maintenance mode.
*Please, just leave it to naturally and
While I agree with this overall, I don’t see why we need 2 GRASS branches. What
is the value in 2 GRASS 6 branches that cannot be achieved with 1 branch?
Michael
__
C. Michael Barton
Director, Center for Social Dynamics Complexity
Professor of Anthropology, School
Michael Barton wrote:
While I agree with this overall, I don�t see why we need 2 GRASS
branches. What is the value in 2 GRASS 6 branches that cannot be
achieved with 1 branch?
If 6.x is going to maintenance-only, we don't need two branches for
it. Just a release branch, with releases as
Moritz Lennert wrote:
In my understanding we were still quite far away from solving the python
on windows issues.
That depends upon what you consider the issue to be.
If the user already has a compatible version of Python and the
required libraries correctly installed, there isn't any
Markus Metz-3 wrote
Since the code base of devbr6 and relbr6 is largely identical,
the same fix can be applied to both branches which is not a lot of
work.
___
grass-psc mailing list
grass-psc at .osgeo
On 06/04/14 13:46, Hamish wrote:
First of all, I believe this discussion belongs on the grass-dev list, not PSC.
See RFC1.
CC'in to dev-list
releasebranch70 should not have been branched until 7.0RC1. Until RC1
it is just wasted effort to keep the two of them as a 1:1 mirror, so
what's
2014-04-06 15:16 GMT+02:00 Moritz Lennert mlenn...@club.worldonline.be:
Hamish, maybe you could be the official grass6 maintainer, managing the
whole grass6 development in the way you propose, i.e. any new development
and bugfixes first go into grass6dev for a period of testing, before _you_
On Sun, Apr 6, 2014 at 3:16 PM, Moritz Lennert
mlenn...@club.worldonline.be wrote:
On 06/04/14 13:46, Hamish wrote:
As mentioned before, I wish to use the bulk of my grass dev time
maintaining the grass 6 line. To do that properly I need a staging
area, and devbr6 is it.
I don't see the
My 1 cent or less...
I think grass7 shold be the focus of the project now, the place where new
stuff should be developed, and that versions 6 are for bugfix only.
Why should I develop something new not in the latest software version?
All this thinking of a good enough version 7 (which I think
I believe that we have a communication problem here rather than a disagreement
about the GRASS6.5:
Hamish says:
GRASS 6.x is already far along into bugfix maintenance mode.
*Please, just leave it to naturally and quietly make its way into history.*
I wish to use the bulk of my grass dev time
+1
I also think we should stop GRASS 6 development
On 6 April 2014 19:01, Martin Landa landa.mar...@gmail.com wrote:
2014-04-06 15:16 GMT+02:00 Moritz Lennert mlenn...@club.worldonline.be:
Hamish, maybe you could be the official grass6 maintainer, managing the
whole grass6 development in
22 matches
Mail list logo
