[GRASS-dev] call for volunteers - urgent need for Windows Vista binaries

Whether you like it or not, it is nearly impossible to get a new PC without Windows Vista today. If we want GRASS to be accessible to Windows users, we need to have versions that run under Vista.

Over the past year, the development team have worked to solve many issues that kept GRASS from running under Vista in the past. The only problem now is that there are no Windows Vista binaries for users. Furthermore, there is no current stand-alone Windows binary for GRASS at all.

Marco Pasetti made a very nice Windows installer for 6.3 last year, but is unable to continue this work.

Other folks in OSGEO have created OSGEO4W with a number of packages. However, GRASS is in the 'advanced' section--and it is not clear what libraries need to be downloaded with it--and it cannot be installed stand-alone.

Also, as far as I can tell, the OSGEO4W binary is compiled with Windows XP. It opens in Vista but various modules insidiously fail (e.g. r.patch, v.patch, v.what.rast, and others). Anyone who installs GRASS under Windows Vista will perceive it as a very buggy and semi-functional program.

So if we are serious about making GRASS as cross-platform as we claim, we need some windows knowledgeable volunteers who can 1) help the OSGEO4W team create a Vista version and 2) produce binary versions of GRASS for XP and Vista to go along with the current Linux and Mac versions. The current GRASS dev team has done a fantastic job over the past 2 years of making GRASS compilable under Windows, but are working hard on maintaining and developing the module and interface code.

So we really need some new volunteers to tackle maintaining Windows binaries. Is there anyone able to take this on?

Michael

Michael,

How about making it a Summer of Code project, perhaps we can find some
windows programmer who wants to help us?

--Wolf

On 26.03.2009 21:21, Michael Barton wrote:

Whether you like it or not, it is nearly impossible to get a new PC
without Windows Vista today. If we want GRASS to be accessible to
Windows users, we need to have versions that run under Vista.

Over the past year, the development team have worked to solve many
issues that kept GRASS from running under Vista in the past. The only
problem now is that there are no Windows Vista binaries for users.
Furthermore, there is no current stand-alone Windows binary for GRASS at
all.

Marco Pasetti made a very nice Windows installer for 6.3 last year, but
is unable to continue this work.

Other folks in OSGEO have created OSGEO4W with a number of packages.
However, GRASS is in the 'advanced' section--and it is not clear what
libraries need to be downloaded with it--and it cannot be installed
stand-alone.

Also, as far as I can tell, the OSGEO4W binary is compiled with Windows
XP. It opens in Vista but various modules insidiously fail (e.g.
r.patch, v.patch, v.what.rast, and others). Anyone who installs GRASS
under Windows Vista will perceive it as a very buggy and semi-functional
program.

So if we are serious about making GRASS as cross-platform as we claim,
we need some windows knowledgeable volunteers who can 1) help the
OSGEO4W team create a Vista version and 2) produce binary versions of
GRASS for XP and Vista to go along with the current Linux and Mac
versions. The current GRASS dev team has done a fantastic job over the
past 2 years of making GRASS compilable under Windows, but are working
hard on maintaining and developing the module and interface code.

So we really need some new volunteers to tackle maintaining Windows
binaries. Is there anyone able to take this on?

Michael
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

--

<:3 )---- Wolf Bergenheim ----( 8:>

hi, just small note:

On Thu, Mar 26, 2009 at 12:21:55PM -0700, Michael Barton wrote:

Marco Pasetti made a very nice Windows installer for 6.3 last year, but
is unable to continue this work.

Other folks in OSGEO have created OSGEO4W with a number of packages.
However, GRASS is in the 'advanced' section--and it is not clear what
libraries need to be downloaded with it--and it cannot be installed
stand-alone.

the osgeo4w installer is just fine, only thing is missing is, that GRASS
should appear in the 'basic' section as well (should not be that
complicated) and all depandances are fixed. than the installation is IMHO enough straight forward and easy.

jachym

--
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/JachymCepicky.pgp
Key fingerprint: 0C6D 0EAE 76BD 506C F299 ED8A C8AB 74B8 08D4 E08F

On Mar 26, 2009, at 10:21 PM, Jachym Cepicky wrote:

hi, just small note:

On Thu, Mar 26, 2009 at 12:21:55PM -0700, Michael Barton wrote:

Marco Pasetti made a very nice Windows installer for 6.3 last year, but
is unable to continue this work.

Other folks in OSGEO have created OSGEO4W with a number of packages.
However, GRASS is in the 'advanced' section--and it is not clear what
libraries need to be downloaded with it--and it cannot be installed
stand-alone.

the osgeo4w installer is just fine, only thing is missing is, that GRASS
should appear in the 'basic' section as well (should not be that
complicated) and all depandances are fixed. than the installation is IMHO enough straight forward and easy.

jachym

Jachym,

The osgeo4w installer does not work well with Vista. The binary seems to have been compiled for XP and so various modules fail when GRASS installed is installed in this way on Vista. There needs to be a Vista version of the installer

Also, while the osteo4w installer is nice for individual installs, it is problematic for institutional lab installs, where IT managers want to have stand alone apps that they can test, install, and remove rather than a suite of apps in a package installer format. It's the same problem I've face with the Cygwin version when trying to use GRASS in university classroom labs. It would help to have the option to install a package as stand alone.

Michael

On 27/03/09 07:18, Michael Barton wrote:

Also, while the osteo4w installer is nice for individual installs, it is problematic for institutional lab installs, where IT managers want to have stand alone apps that they can test, install, and remove rather than a suite of apps in a package installer format. It's the same problem I've face with the Cygwin version when trying to use GRASS in university classroom labs. It would help to have the option to install a package as stand alone.

Creating such standalone packages should not be too hard using osgeo4w as a starting point. See

http://trac.osgeo.org/osgeo4w/wiki/FAQ#HowdoIperformanofflineorcomputerlabinstall
("How do I perform an offline or computer lab install?")

and the blog referenced there:
http://blog.qgis.org/node/124

Moritz

Jachym,

I have to echo what Michael is saying about the Windows installer. In a government enterprise environment, I doubt the present osgeo installation format would be accepted. A stand-alone msi package would be better.

Another question with the osgeo installer, would the installation of the support libraries/utilites ( python, gdal, etc.) conflict with an existing installation of ArcGIS and it’s libraries? I’m trying to get folks who already use ArcGIS to try doing some things in GRASS.

The combination of an unfamiliar installation package and conflicts with their existing software would increase the resistance to initial use.

Doug

Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.gov

The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of Interior. Life is too short for undocumented, proprietary data formats.
Inactive hide details for Michael Barton <Michael.Barton@asu.edu>Michael Barton Michael.Barton@asu.edu

Michael Barton <Michael.Barton@asu.edu>
Sent by: grass-dev-bounces@lists.osgeo.org

03/27/2009 02:18 AM

To

Jachym Cepicky <jachym.cepicky@gmail.com>

cc

grass-user grass-user <grass-user@lists.osgeo.org>, GRASS developers list <grass-dev@lists.osgeo.org>

Subject

Re: [GRASS-dev] call for volunteers - urgent need for Windows Vista binaries

On Mar 26, 2009, at 10:21 PM, Jachym Cepicky wrote:

> hi, just small note:
>
> On Thu, Mar 26, 2009 at 12:21:55PM -0700, Michael Barton wrote:
>> Marco Pasetti made a very nice Windows installer for 6.3 last year,
>> but
>> is unable to continue this work.
>>
>> Other folks in OSGEO have created OSGEO4W with a number of packages.
>> However, GRASS is in the 'advanced' section--and it is not clear what
>> libraries need to be downloaded with it--and it cannot be installed
>> stand-alone.
>>
>
> the osgeo4w installer is just fine, only thing is missing is, that
> GRASS
> should appear in the 'basic' section as well (should not be that
> complicated) and all depandances are fixed. than the installation is
> IMHO enough straight forward and easy.
>
> jachym

Jachym,

The osgeo4w installer does not work well with Vista. The binary seems
to have been compiled for XP and so various modules fail when GRASS
installed is installed in this way on Vista. There needs to be a Vista
version of the installer

Also, while the osteo4w installer is nice for individual installs, it
is problematic for institutional lab installs, where IT managers want
to have stand alone apps that they can test, install, and remove
rather than a suite of apps in a package installer format. It's the
same problem I've face with the Cygwin version when trying to use
GRASS in university classroom labs. It would help to have the option
to install a package as stand alone.

Michael

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
[http://lists.osgeo.org/mailman/listinfo/grass-dev](http://lists.osgeo.org/mailman/listinfo/grass-dev)

(attachments)

pic00236.gif

Thanks Moritz,

I'm glad to see that this is possible at least, though it is by no means obvious. I will try to find a place to archive this information as I will be again doing a lab course later this spring. The fact that critical information for creating a stand-alone package is buried in a blog is problematic--though I know that all are very pressed for time. What happens is you want to do 2 separate stand alone packages? Do the libraries conflict? I'm just not well enough versed (i.e., ignorant) in Windows, and especially Vista, to know about this.

Michael

On Mar 27, 2009, at 2:27 AM, Moritz Lennert wrote:

On 27/03/09 07:18, Michael Barton wrote:

Also, while the osteo4w installer is nice for individual installs, it is problematic for institutional lab installs, where IT managers want to have stand alone apps that they can test, install, and remove rather than a suite of apps in a package installer format. It's the same problem I've face with the Cygwin version when trying to use GRASS in university classroom labs. It would help to have the option to install a package as stand alone.

Creating such standalone packages should not be too hard using osgeo4w as a starting point. See

FAQ – OSGeo4W
("How do I perform an offline or computer lab install?")

and the blog referenced there:
http://blog.qgis.org/node/124

Moritz

On Fri, Mar 27, 2009 at 4:17 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

Thanks Moritz,

I'm glad to see that this is possible at least, though it is by no means
obvious. I will try to find a place to archive this information as I will be
again doing a lab course later this spring. The fact that critical
information for creating a stand-alone package is buried in a blog is
problematic--though I know that all are very pressed for time.

easy to solve: I have added it here:
http://trac.osgeo.org/osgeo4w/wiki/pkg-grass
-> Lab Installation as offline set of packages

It would not harm of course to move the relevant into to that trac
page rather thank linking around.

Markus

Thanks Markus,

This will make the information more accessible.

Michale

On Mar 27, 2009, at 8:41 AM, Markus Neteler wrote:

On Fri, Mar 27, 2009 at 4:17 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

Thanks Moritz,

I'm glad to see that this is possible at least, though it is by no means
obvious. I will try to find a place to archive this information as I will be
again doing a lab course later this spring. The fact that critical
information for creating a stand-alone package is buried in a blog is
problematic--though I know that all are very pressed for time.

easy to solve: I have added it here:
pkg-grass – OSGeo4W
-> Lab Installation as offline set of packages

It would not harm of course to move the relevant into to that trac
page rather thank linking around.

Markus

Michael,
I have just tried r.patch, v.patch and v.what.rast on the new
grass-6.4.svn release in osgeo4w (built on XP I assume), and haven't
had any problems with any of them. So perhaps these issues have been
solved.

Maybe I'm missing it somewhere in the many wiki pages, but is there a
complete list of vista related issues for me/others to test?
http://grass.osgeo.org/wiki/WinGRASS_Current_Status#Vista seems not to
have been updated recently.

My two cents: I agree that an standalone installer is vastly
preferable to the osgeo4w format for the majority of windows users. I
have heard that Marco is not able to continue to supply these
installers, but did he document the steps required to create
installers somewhere? With the osgeo4w installer allowing for quick
compiles of new grass versions, there should be no reason why these
can't be continued.

-Colin

On Fri, Mar 27, 2009 at 12:24 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

Thanks Markus,

This will make the information more accessible.

Michale

On Mar 27, 2009, at 8:41 AM, Markus Neteler wrote:

On Fri, Mar 27, 2009 at 4:17 PM, Michael Barton <Michael.Barton@asu.edu>
wrote:

Thanks Moritz,

I'm glad to see that this is possible at least, though it is by no means
obvious. I will try to find a place to archive this information as I will
be
again doing a lab course later this spring. The fact that critical
information for creating a stand-alone package is buried in a blog is
problematic--though I know that all are very pressed for time.

easy to solve: I have added it here:
http://trac.osgeo.org/osgeo4w/wiki/pkg-grass
-> Lab Installation as offline set of packages

It would not harm of course to move the relevant into to that trac
page rather thank linking around.

Markus

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

I should have looked harder before I hit "Send", I just found Marco's
instructions on creating the standalone installer.
<http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/mswindows&gt;

If modified to the osgeo4w tree, new native installers should be
relatively easy to create. The wingrass team seems to be a little
divided right now (native, mingw/msys, osgeo4w, cygwin, not to mention
lots of different user & developer wiki pages saying different
things), is there a consensus on where to take wingrass? (I should
note that I'm relatively new to the scene and therefore may be missing
longer-term trends and discussions.)

-Colin

On Mon, Mar 30, 2009 at 7:29 PM, Colin Nielsen <colin.nielsen@gmail.com> wrote:

Michael,
I have just tried r.patch, v.patch and v.what.rast on the new
grass-6.4.svn release in osgeo4w (built on XP I assume), and haven't
had any problems with any of them. So perhaps these issues have been
solved.

Maybe I'm missing it somewhere in the many wiki pages, but is there a
complete list of vista related issues for me/others to test?
http://grass.osgeo.org/wiki/WinGRASS_Current_Status#Vista seems not to
have been updated recently.

My two cents: I agree that an standalone installer is vastly
preferable to the osgeo4w format for the majority of windows users. I
have heard that Marco is not able to continue to supply these
installers, but did he document the steps required to create
installers somewhere? With the osgeo4w installer allowing for quick
compiles of new grass versions, there should be no reason why these
can't be continued.

-Colin

On Fri, Mar 27, 2009 at 12:24 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

Thanks Markus,

This will make the information more accessible.

Michale

On Mar 27, 2009, at 8:41 AM, Markus Neteler wrote:

On Fri, Mar 27, 2009 at 4:17 PM, Michael Barton <Michael.Barton@asu.edu>
wrote:

Thanks Moritz,

I'm glad to see that this is possible at least, though it is by no means
obvious. I will try to find a place to archive this information as I will
be
again doing a lab course later this spring. The fact that critical
information for creating a stand-alone package is buried in a blog is
problematic--though I know that all are very pressed for time.

easy to solve: I have added it here:
http://trac.osgeo.org/osgeo4w/wiki/pkg-grass
-> Lab Installation as offline set of packages

It would not harm of course to move the relevant into to that trac
page rather thank linking around.

Markus

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Native, stand alone installer for GRASS should be a high priority. I guess we need both an XP and Vista version.

Michael

On Mar 30, 2009, at 4:41 PM, Colin Nielsen wrote:

I should have looked harder before I hit "Send", I just found Marco's
instructions on creating the standalone installer.
<http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/mswindows&gt;

If modified to the osgeo4w tree, new native installers should be
relatively easy to create. The wingrass team seems to be a little
divided right now (native, mingw/msys, osgeo4w, cygwin, not to mention
lots of different user & developer wiki pages saying different
things), is there a consensus on where to take wingrass? (I should
note that I'm relatively new to the scene and therefore may be missing
longer-term trends and discussions.)

-Colin

On Mon, Mar 30, 2009 at 7:29 PM, Colin Nielsen <colin.nielsen@gmail.com> wrote:

Michael,
I have just tried r.patch, v.patch and v.what.rast on the new
grass-6.4.svn release in osgeo4w (built on XP I assume), and haven't
had any problems with any of them. So perhaps these issues have been
solved.

Maybe I'm missing it somewhere in the many wiki pages, but is there a
complete list of vista related issues for me/others to test?
WinGRASS Current Status - GRASS-Wiki seems not to
have been updated recently.

My two cents: I agree that an standalone installer is vastly
preferable to the osgeo4w format for the majority of windows users. I
have heard that Marco is not able to continue to supply these
installers, but did he document the steps required to create
installers somewhere? With the osgeo4w installer allowing for quick
compiles of new grass versions, there should be no reason why these
can't be continued.

-Colin

On Fri, Mar 27, 2009 at 12:24 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

Thanks Markus,

This will make the information more accessible.

Michale

On Mar 27, 2009, at 8:41 AM, Markus Neteler wrote:

On Fri, Mar 27, 2009 at 4:17 PM, Michael Barton <Michael.Barton@asu.edu>
wrote:

Thanks Moritz,

I'm glad to see that this is possible at least, though it is by no means
obvious. I will try to find a place to archive this information as I will
be
again doing a lab course later this spring. The fact that critical
information for creating a stand-alone package is buried in a blog is
problematic--though I know that all are very pressed for time.

easy to solve: I have added it here:
pkg-grass – OSGeo4W
-> Lab Installation as offline set of packages

It would not harm of course to move the relevant into to that trac
page rather thank linking around.

Markus

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
grass-user Info Page

MIlton,

This is great. My only concern is how to successfully package and distribute this to others. I’ve been working with Colin Nielsen, who has kindly provided a couple of vista binaries in the past week and we can’t get either to work so far. The seem to need additional dll’s that are hidden somewhere in the system.

I’m sure that there must be a way to package this up, but I don’t know what it is.

Michael


C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>

On Mar 30, 2009, at 7:12 PM, Milton Cezar Ribeiro wrote:

I Just compiled grass6.5 under Msys Vista 64b, but I don’t know if it helps.
I am not familiar with the generation of installer, but I can share the directories with the grass structure…

Bests

miltinho

2009/3/26 Michael Barton <Michael.Barton@asu.edu>

Whether you like it or not, it is nearly impossible to get a new PC without Windows Vista today. If we want GRASS to be accessible to Windows users, we need to have versions that run under Vista.

Over the past year, the development team have worked to solve many issues that kept GRASS from running under Vista in the past. The only problem now is that there are no Windows Vista binaries for users. Furthermore, there is no current stand-alone Windows binary for GRASS at all.

Marco Pasetti made a very nice Windows installer for 6.3 last year, but is unable to continue this work.

Other folks in OSGEO have created OSGEO4W with a number of packages. However, GRASS is in the ‘advanced’ section–and it is not clear what libraries need to be downloaded with it–and it cannot be installed stand-alone.

Also, as far as I can tell, the OSGEO4W binary is compiled with Windows XP. It opens in Vista but various modules insidiously fail (e.g. r.patch, v.patch, v.what.rast, and others). Anyone who installs GRASS under Windows Vista will perceive it as a very buggy and semi-functional program.

So if we are serious about making GRASS as cross-platform as we claim, we need some windows knowledgeable volunteers who can 1) help the OSGEO4W team create a Vista version and 2) produce binary versions of GRASS for XP and Vista to go along with the current Linux and Mac versions. The current GRASS dev team has done a fantastic job over the past 2 years of making GRASS compilable under Windows, but are working hard on maintaining and developing the module and interface code.

So we really need some new volunteers to tackle maintaining Windows binaries. Is there anyone able to take this on?

Michael


grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Colin,

Marco's installer has been a great success here (both on Vista and XP)
and students greatly appreciate
also the msys console that gives them lot of convenient linux tools.
So if you could rebuild the installer with GRASS64 it would be greatly appreciated.

thanks a lot for your work,

Helena

P.S. the only issue (minor) that I had was that he re-named the nc_spm data set to
NORTH-CAROLINA causing some confusion because the name is
different from the one used in the GRASSbook and we also have North
Carolina in other coordinate systems (nc_ll and nc_spf). But that is just cosmetics.

On Mar 30, 2009, at 7:41 PM, Colin Nielsen wrote:

I should have looked harder before I hit "Send", I just found Marco's
instructions on creating the standalone installer.
<http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/mswindows&gt;

If modified to the osgeo4w tree, new native installers should be
relatively easy to create. The wingrass team seems to be a little
divided right now (native, mingw/msys, osgeo4w, cygwin, not to mention
lots of different user & developer wiki pages saying different
things), is there a consensus on where to take wingrass? (I should
note that I'm relatively new to the scene and therefore may be missing
longer-term trends and discussions.)

-Colin

On Mon, Mar 30, 2009 at 7:29 PM, Colin Nielsen <colin.nielsen@gmail.com> wrote:

Michael,
I have just tried r.patch, v.patch and v.what.rast on the new
grass-6.4.svn release in osgeo4w (built on XP I assume), and haven't
had any problems with any of them. So perhaps these issues have been
solved.

Maybe I'm missing it somewhere in the many wiki pages, but is there a
complete list of vista related issues for me/others to test?
http://grass.osgeo.org/wiki/WinGRASS_Current_Status#Vista seems not to
have been updated recently.

My two cents: I agree that an standalone installer is vastly
preferable to the osgeo4w format for the majority of windows users. I
have heard that Marco is not able to continue to supply these
installers, but did he document the steps required to create
installers somewhere? With the osgeo4w installer allowing for quick
compiles of new grass versions, there should be no reason why these
can't be continued.

-Colin

On Fri, Mar 27, 2009 at 12:24 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

Thanks Markus,

This will make the information more accessible.

Michale

On Mar 27, 2009, at 8:41 AM, Markus Neteler wrote:

On Fri, Mar 27, 2009 at 4:17 PM, Michael Barton <Michael.Barton@asu.edu>
wrote:

Thanks Moritz,

I'm glad to see that this is possible at least, though it is by no means
obvious. I will try to find a place to archive this information as I will
be
again doing a lab course later this spring. The fact that critical
information for creating a stand-alone package is buried in a blog is
problematic--though I know that all are very pressed for time.

easy to solve: I have added it here:
http://trac.osgeo.org/osgeo4w/wiki/pkg-grass
-> Lab Installation as offline set of packages

It would not harm of course to move the relevant into to that trac
page rather thank linking around.

Markus

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Hi,

2009/3/31 Michael Barton <Michael.Barton@asu.edu>:

Native, stand alone installer for GRASS should be a high priority. I guess
we need both an XP and Vista version.

personally I have no problem with osgeo4w installer. Ideally should be
mentained both - standalone and osgeo4w - if we have enough manpower.
If no, I would incline to osgeo4w.

1CZK

M.

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

I'm working on the installer, I think I've almost got it. I'll post an
update in the next couple of days. I'm working on Vista, so that's
what I'll be packaging, but as long as the vista version doesn't cause
problems in xp (and as far as i know it doesn't) we shouldn't need two
windows packages.

-Colin

On Tue, Mar 31, 2009 at 12:58 AM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2009/3/31 Michael Barton <Michael.Barton@asu.edu>:

Native, stand alone installer for GRASS should be a high priority. I guess
we need both an XP and Vista version.

personally I have no problem with osgeo4w installer. Ideally should be
mentained both - standalone and osgeo4w - if we have enough manpower.
If no, I would incline to osgeo4w.

1CZK

M.

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

That would be excellent.

With some interface tweaking, I have nothing inherently against the osgeo4w installer, but a stand alone along the lines of what you are preparing will be a big help in a number of cases, especially in universities and other large institutions where we are trying to get people to consider open source.

It may even get people to try the osgeo4w installer for the other apps if it is successful.

Michael
______________________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ 85287-2402
USA

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

On Mar 31, 2009, at 10:25 AM, Colin Nielsen wrote:

I'm working on the installer, I think I've almost got it. I'll post an
update in the next couple of days. I'm working on Vista, so that's
what I'll be packaging, but as long as the vista version doesn't cause
problems in xp (and as far as i know it doesn't) we shouldn't need two
windows packages.

-Colin

On Tue, Mar 31, 2009 at 12:58 AM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2009/3/31 Michael Barton <Michael.Barton@asu.edu>:

Native, stand alone installer for GRASS should be a high priority. I guess
we need both an XP and Vista version.

personally I have no problem with osgeo4w installer. Ideally should be
mentained both - standalone and osgeo4w - if we have enough manpower.
If no, I would incline to osgeo4w.

1CZK

M.

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

On 31/03/09 06:58, Martin Landa wrote:

Hi,

2009/3/31 Michael Barton <Michael.Barton@asu.edu>:

Native, stand alone installer for GRASS should be a high priority. I guess
we need both an XP and Vista version.

personally I have no problem with osgeo4w installer. Ideally should be
mentained both - standalone and osgeo4w - if we have enough manpower.
If no, I would incline to osgeo4w.

I can only repeat that the two are not opposed, but that you can create a standalone installer on the basis of osgeo4w:

http://trac.osgeo.org/osgeo4w/wiki/FAQ#HowdoIperformanofflineorcomputerlabinstall

AFAICT, you just need to create the .bat file mentioned in the QGIS blog and you have a clickable installer.

Moritz

On 02/04/09 18:51, Michael Barton wrote:

Thanks. This is good to know. Of course the user/lab manager still needs to create a *.bat file from instructions in a blog (at least now referenced on the WIKI).

No, what I meant is that with the osgeo4w installation environment, someone could package a stand-alone GRASS installer and make it available via the GRASS web site. Seems more sustainable to me than having separate efforts going into a stand-alone installer and osgeo4w. I guess someone would have to try the osgeo4w path to an installer once to see how user and lab-friendly this really is.

Moritz

Michael
______________________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ 85287-2402
USA

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

On Apr 2, 2009, at 2:06 AM, Moritz Lennert wrote:

On 31/03/09 06:58, Martin Landa wrote:

Hi,
2009/3/31 Michael Barton <Michael.Barton@asu.edu>:

Native, stand alone installer for GRASS should be a high priority. I guess
we need both an XP and Vista version.

personally I have no problem with osgeo4w installer. Ideally should be
mentained both - standalone and osgeo4w - if we have enough manpower.
If no, I would incline to osgeo4w.

I can only repeat that the two are not opposed, but that you can create a standalone installer on the basis of osgeo4w:

http://trac.osgeo.org/osgeo4w/wiki/FAQ#HowdoIperformanofflineorcomputerlabinstall

AFAICT, you just need to create the .bat file mentioned in the QGIS blog and you have a clickable installer.

Moritz

Ohhh!

This indeed makes sense. We still need a vista version. But the less duplication the better.

Michael

On Apr 2, 2009, at 1:10 PM, Moritz Lennert wrote:

On 02/04/09 18:51, Michael Barton wrote:

Thanks. This is good to know. Of course the user/lab manager still needs to create a *.bat file from instructions in a blog (at least now referenced on the WIKI).

No, what I meant is that with the osgeo4w installation environment, someone could package a stand-alone GRASS installer and make it available via the GRASS web site. Seems more sustainable to me than having separate efforts going into a stand-alone installer and osgeo4w. I guess someone would have to try the osgeo4w path to an installer once to see how user and lab-friendly this really is.

Moritz

Michael
______________________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
On Apr 2, 2009, at 2:06 AM, Moritz Lennert wrote:

On 31/03/09 06:58, Martin Landa wrote:

Hi,
2009/3/31 Michael Barton <Michael.Barton@asu.edu>:

Native, stand alone installer for GRASS should be a high priority. I guess
we need both an XP and Vista version.

personally I have no problem with osgeo4w installer. Ideally should be
mentained both - standalone and osgeo4w - if we have enough manpower.
If no, I would incline to osgeo4w.

I can only repeat that the two are not opposed, but that you can create a standalone installer on the basis of osgeo4w:

FAQ – OSGeo4W

AFAICT, you just need to create the .bat file mentioned in the QGIS blog and you have a clickable installer.

Moritz