<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: R: [GRASS-dev] GRASS 6.3.0 to be released</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=328522518-16042008><FONT face=Verdana
size=2>Hi Michael,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=328522518-16042008><FONT face=Verdana
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=328522518-16042008><FONT face=Verdana
size=2><FONT color=#0000ff>><FONT face=Calibri size=3>If it’s easier to just
do a single package, then I think that is what you should do. That is what most
Windows (and Mac) users expect anyway.</FONT></FONT><BR></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=328522518-16042008><FONT face=Verdana
size=2>...and that's very good to hear for me ;-)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=328522518-16042008><FONT face=Verdana
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=328522518-16042008><FONT face=Verdana
size=2>Marco</DIV></FONT></SPAN><BR>
<DIV class=OutlookMessageHeader lang=it dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>Da:</B> Michael Barton
[mailto:michael.barton@asu.edu] <BR><B>Inviato:</B> mercoledì 16 aprile 2008
19.16<BR><B>A:</B> marco.pasetti@alice.it;
grass-dev@lists.osgeo.org<BR><B>Oggetto:</B> Re: R: [GRASS-dev] GRASS 6.3.0 to
be released<BR></FONT><BR></DIV>
<DIV></DIV><FONT size=4><FONT face="Calibri, Verdana, Helvetica, Arial"><SPAN
style="FONT-SIZE: 11pt">You have described it well. If it’s easier to just do a
single package, then I think that is what you should do. That is what most
Windows (and Mac) users expect anyway.<BR><BR>Michael<BR><BR><BR>On 4/16/08 9:40
AM, "marco.pasetti@alice.it" <marco.pasetti@alice.it>
wrote:<BR><BR></SPAN></FONT></FONT>
<BLOCKQUOTE><FONT size=4><SPAN style="FONT-SIZE: 11pt"><FONT
face=Arial>Michael,<BR></FONT><FONT
face="Calibri, Verdana, Helvetica, Arial"><BR>>I see what you mean on
Windows. Actually, in this case, there are no<BR>>dependencies like you
find on Unix systems<BR> <BR>thx. it's difficult to be a Windows user
here. GRASS people is used to work on too much advanced systems than I'm used
to ;-) (even if I'm a linux user too)<BR> <BR>>A separate install for
Msys/TclTk/Python might be
useful.<BR> <BR>MSYS:<BR>-----------------------<BR>I think we could
provide MSYS as install option or don't provide it at all... if people want
MSYS they can download and install using the official MSYS installer (the
GRASS installer could just check if MSYS is installed and create the grass63
file into /usr msys folder, according to selected GRASS install path, as it
already does)<BR> <BR>TclTk<BR>-----------------------<BR>This is needed,
since GRASS is built with it and some binaries require tcl/tk DLLs. I think we
must provide it along
binaries<BR> <BR>Python<BR>-----------------------<BR>I think that's the
only indipendent package installer we could provide.<BR> <BR>>Then
that part could be installed only as<BR>>needed and GRASS could be updated
more often.<BR> <BR>I think that's not a *frequency* problem, but just a
*weight* problem of the installers provided.<BR> <BR>If I had built a new
version of GRASS to release, it's not absolutely a problem for me to package
all the other files along with it (I mean the new GRASS build) as I as did
with the WinGRASS-6.3.0RC5 and RC6 releases. I need to just run an automated
batch file I wrote for the job, and then compile the NSIS script to create the
related installer. The whole packaging job takes approx 5
minutes!<BR> <BR>I hope to have well described the
*situation*<BR> <BR>Best regards,<BR> <BR>Marco<BR> <BR><BR>
<HR align=center width="100%" SIZE=3>
</FONT><FONT face="Tahoma, Verdana, Helvetica, Arial"><B>Da:</B>
grass-dev-bounces@lists.osgeo.org per conto di Michael
Barton<BR><B>Inviato:</B> mer 16/04/2008 18.15<BR><B>A:</B>
grass-dev@lists.osgeo.org<BR><B>Oggetto:</B> Re: [GRASS-dev] GRASS 6.3.0 to be
released<BR></FONT><FONT
face="Calibri, Verdana, Helvetica, Arial"><BR>Marco,<BR><BR>I see what you
mean on Windows. Actually, in this case, there are no<BR>dependencies like you
find on Unix systems. A separate install for<BR>Msys/TclTk/Python might be
useful. Then that part could be installed only as<BR>needed and GRASS could be
updated more often.<BR><BR>Michael<BR><BR><BR>On 4/16/08 9:00 AM,
"grass-dev-request@lists.osgeo.org"<BR><grass-dev-request@lists.osgeo.org>
wrote:<BR><BR>> Date: Wed, 16 Apr 2008 17:18:30 +0200<BR>> From:
<marco.pasetti@alice.it><BR>> Subject: R: R: R: [GRASS-dev] GRASS
6.3.0 to be released<BR>> To: "Moritz Lennert"
<mlennert@club.worldonline.be><BR>> Cc: Martin Landa
<landa.martin@gmail.com>, Glynn Clements<BR>>
<glynn@gclements.plus.com>, GRASS developers list<BR>>
<grass-dev@lists.osgeo.org><BR>> Message-ID:<BR>>
<FA8A693893F4CE4283B4473C79FA47D505BB4184@FBCMST06V02.fbc.local><BR>>
Content-Type: text/plain; charset="iso-8859-1"<BR>><BR>> Hi
Moritz,<BR>> <BR>>> This actually sounds much more sophisticated than
what Glynn proposed.<BR>> <BR>> yes, it is... but we could make a
walkaround... I'll explain how later...<BR>> <BR>>> Could you not
simply propose one installer with only the latest<BR>>> (complete) GRASS
binaries. This installer could check for any existing<BR>>> installation
of GRASS and propose to erase that before installing the<BR>>> new
version, or install the new version next to the old.<BR>> <BR>> very
good ;-) we are at the same *point* here. I already thought it some
weeks<BR>> ago, before ro release RC6... and that's why I already added in
RC6 installer<BR>> some registry key values that would let me the job (that
is: let future<BR>> installers recognise if GRASS is already istalled on
the system, what version<BR>> and where). I already talked with Markus
about this option in future WinGRASS<BR>> installers.<BR>> <BR>>>
The question then is: do we need a "complete" installer with
everything<BR>>> in it (as you suggest), or can we impose the burden of
two installers on<BR>>> people, i.e. as Glynn suggests: one GRASS
installer + one Dependencies<BR>>> installer. I think this would be the
best solution for us, but it would<BR>>> mean that at least for the
first installation, users will have to<BR>>> install two packages. If
the GRASS installer could test for the<BR>>> installation of the other
package and propose to download it and lauch<BR>>> its installation
autmagically, then this might be the best solution.<BR>> <BR>> what do
you mean about *dependencies*? the only dependencies that are<BR>>
indipendent to GRASS binaries is Python!<BR>> all the other DLLs are
necessary to start GRASS. What would happen if we<BR>> release GRASS with
an additional support (jpeg, for example) not previously<BR>> supported? we
must provide the libjpeg with the installer, or update the<BR>>
*dependencies installer*?<BR>> IMHO, this is a sctrictly UNIX way to
think... windows is very different: if<BR>> you release binaries, you must
provide all the DLLs needed by those binaries<BR>> along with them.<BR>>
It would be a *safer* solution to release future WinGRASS installers
along<BR>> with a separated updater: in that way new users would install
the whole GRASS<BR>> package (why provide 2 different installers when users
absolutely need to<BR>> install both GRASS bins and Deps?) or simply
download and lunch a smaller<BR>> updater, that would copy/replace only the
new bins and libs.<BR>> <BR>> BTW, I still think that providing
separated installers for GRASS and its<BR>> dependencies is a
nonsense...<BR>> <BR>> Best regards,<BR>> <BR>>
Marco<BR><BR>__________________________________________<BR>Michael Barton,
Professor of Anthropology<BR>Director of Graduate Studies<BR>School of Human
Evolution & Social Change<BR>Center for Social Dynamics &
Complexity<BR>Arizona State University<BR><BR>phone: 480-965-6213<BR>fax:
480-965-7671<BR>www: <A
href="http://www.public.asu.edu/~cmbarton">http://www.public.asu.edu/~cmbarton</A><BR><BR><BR>_______________________________________________<BR>grass-dev
mailing list<BR>grass-dev@lists.osgeo.org<BR><A
href="http://lists.osgeo.org/mailman/listinfo/grass-dev">http://lists.osgeo.org/mailman/listinfo/grass-dev</A><BR><BR></FONT></SPAN></FONT></BLOCKQUOTE><FONT
size=4><SPAN style="FONT-SIZE: 11pt"><FONT
face="Calibri, Verdana, Helvetica, Arial"><BR>__________________________________________<BR>Michael
Barton, Professor of Anthropology<BR>Director of Graduate Studies<BR>School of
Human Evolution & Social Change <BR>Center for Social
Dynamics & Complexity<BR>Arizona State University<BR><BR>phone:
480-965-6213<BR>fax: 480-965-7671<BR>www: <A
href="http://www.public.asu.edu/~cmbarton">http://www.public.asu.edu/~cmbarton</A>
<BR><BR></FONT></SPAN></FONT></BODY></HTML>