Re: R: R: R: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer
On 12/03/08 21:32, Marco Pasetti wrote:
Hi Glynn,
Please note that, if you provide binaries which are covered by the GPL, you
must provide the corresponding source code for download *from the same
place*. It isn't sufficient to point to the source on a different site.
[...]
I think that this is a problem I should don't care, actually. I asked the
list if there were problems about that and I had the green light... If you
don't agree, I think you should discuss the matter with other persons, I
don't have the knowledge to neither reply nor discuss it.
I don't think this is an appropriate answer. Glynn did not necessarily
mean that you are the one that has to host these files. In fact they
should be on the osgeo GRASS site next to the installer, but to just
shrug it off this way is not the way to go. Making sources available is
a fundamental element of free software.
Also, just to correct things a bit, this was discussed before, offlist:
On 29/02/08 18:02, Moritz Lennert wrote:
> On 29/02/08 11:04, [EMAIL PROTECTED] wrote:
>
>> >This said, if we start to officially distribute binary packages with
>> the
>> >libraries included, we also have to make the source code of all these
>> >libraries (and obvioiusly of GRASS) available...
>>
>> sorry, that's my fault... ;-) I meant only to prepare a self installer
>> of GRASS
>
> Well, de facto we are already officially distributing packages, but they
> have been declared "experimental", so maybe we can argue this as an
> excuse. I always meant to do the work you just did and recompile
> everything and then keep the source code. I think that if you could
> provide the binary package plus a directory which contains all the
> source tarballs you used and your compilation information, this would be
> perfect. If you rather have me host these files, I can do so as well.
So, to shorten a long discussion, I just used this simple command line
to download all the source packages mentioned in your guide:
for i in `grep "source code" BuildFromSource.html | awk -F'=' '{print
$3}' | awk -F'"' '{print $2}' | sort`; do wget $i; done
And I downloaded the msys, flex and bison sources manually.
Everything is available at
http://geog-pc40.ulb.ac.be/grass/wingrass/wingrass_sources/ including
the version of the GRASS sources you used (don't think this is
necessary, but just to be complete). All packages are available
individually, and there also is a wingrass_sources.tar which contains
them all.
Maybe Markus can just get the tar and put it on the download site next
to the installer ?
I hope you understand that this is an attempt to make your work even
more perfect than it already is :-)
What's the problem with spaces? If any part of GRASS can't handle spaces in
filenames, that's a bug which should be fixed.
I think that forcing users to install GRASS in a "space free" dir is, at the
moment, the only solution to let us distribute winGRASS with a simple
"one-touch" installation procedure.
Again, I agree with Glynn: if there is a problem let's try to fix it and
not circumvent it. Your great installer will help a lot in getting
people to install and test GRASS on windows, but if we already force
such "solutions" on them, they will not be able to correctly detect the
problem. Is there a way of just making the installer print a warning,
instead of breaking off the installation procedure.
Just looking at your building guide [2], I see that you do not do a
'make install' but copy the files directly from the dist.* dir to
$GISBASE. Actually the 'make install' step is necessary as this corrects
a series of path issues in the files for windows. This might be the
cause of your problems with spaces (although I'm only guessing - I'll
try to install my package in a directory with spaces to test). Any
specific reason why you did not want to go through the make install step ?
Moritz
[1]
- MSYS (1.0.11)
- Flex (2.5.4a-1)
- Bison (2.1)
- Zlib (1.2.3)
- Libpng (1.2.24)
- Libtiff (3.8.2)
- Xdr (4.0)
- Freetype (2.3.5)
- FFTW (3.1.2)
- PDCurses (3.3)
- PROJ.4 (4.6.0)
- GEOS (2.2.3)
- PostgreSQL (8.2.6)
- SQLite (3.5.6)
- GDAL (1.5.0) *
- Tcl/Tk (8.5.1)
[2] http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: R: R: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer
Marco Pasetti wrote: > >What's the problem with spaces? If any part of GRASS can't handle spaces in > filenames, that's a bug which should be fixed. > > I would like to fix the problem too. Actually I spent some time on the > installer script to configure GRASS in order to let it work also in dirs > with spaces (in the first edition, in fact, installer used > %PROGRAMFILES%\GRASS-6.3.0 as standard install dir, that means, for english > versions of Windows, C:\Program Files\GRASS-6.3.0); but, after completing > the installer with success, I discovered that there are many things in GRASS > that definetely don't work because that "spaced" intallation directory: no > help pages, no NVIZ... Please provide details. What you tried, what happened, any error messages etc. The extent to which GRASS works on Windows depends to a very large extent on whether people who experience problems provide us with enough information to actually do something about it. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
R: R: R: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer
Hi Glynn, >Please note that, if you provide binaries which are covered by the GPL, you must provide the corresponding source code for download *from the same place*. It isn't sufficient to point to the source on a different site. >Alternatively, you can provide a written offer to supply the source code upon request, but that means that you have to keep those exact versions of the source code handy for the next 3 years (the website where you obtained it may cease to provide it when a new version is released). I think that this is a problem I should don't care, actually. I asked the list if there were problems about that and I had the green light... If you don't agree, I think you should discuss the matter with other persons, I don't have the knowledge to neither reply nor discuss it. >What's the problem with spaces? If any part of GRASS can't handle spaces in filenames, that's a bug which should be fixed. I would like to fix the problem too. Actually I spent some time on the installer script to configure GRASS in order to let it work also in dirs with spaces (in the first edition, in fact, installer used %PROGRAMFILES%\GRASS-6.3.0 as standard install dir, that means, for english versions of Windows, C:\Program Files\GRASS-6.3.0); but, after completing the installer with success, I discovered that there are many things in GRASS that definetely don't work because that "spaced" intallation directory: no help pages, no NVIZ... I think that forcing users to install GRASS in a "space free" dir is, at the moment, the only solution to let us distribute winGRASS with a simple "one-touch" installation procedure. BTW you can consider that if you (user) have administrative limitations, you can ask your Administrator to let you install GRASS in C:\GRASS... You're not installing Pacman ;-) ... And then you can always store and access your data from GRASS in a usual C:\Documents and settings\Glynn\Documents\Whatever You Want With Lots Of Spaces folder... It works, I swear :-) Marco -Messaggio originale- Da: Glynn Clements [mailto:[EMAIL PROTECTED] Inviato: mercoledì 12 marzo 2008 20.34 A: Marco Pasetti Cc: 'Michael Barton'; grass-dev@lists.osgeo.org Oggetto: Re: R: R: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer Marco Pasetti wrote: > In the pure MS style, installer includes all: tcl/tk, sqlite, > postgresql (the last only dll) built from source, and prebuilt msys > from sourceforge project. Please note that, if you provide binaries which are covered by the GPL, you must provide the corresponding source code for download *from the same place*. It isn't sufficient to point to the source on a different site. Alternatively, you can provide a written offer to supply the source code upon request, but that means that you have to keep those exact versions of the source code handy for the next 3 years (the website where you obtained it may cease to provide it when a new version is released). > Moreover, the installer procedure forces the user to install GRASS in > a path without spaces, to let it wotk properly, What's the problem with spaces? If any part of GRASS can't handle spaces in filenames, that's a bug which should be fixed. Also, some users may not be able to satisfy that requirement. The normal location for installing software often has spaces in the pathname (e.g. "C:\Program Files" on English language versions of Windows), as does the user's data directory (e.g. "C:\Documents and Setttings\"). All users can create files in their data directory, while the "Program Files" directory is normally writable by members of the "Power Users" group. OTOH, creating a new directory outside of those two locations may not be possible if the user isn't in the Administrators group. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: R: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer
Marco Pasetti wrote: > In the pure MS style, installer includes all: tcl/tk, sqlite, postgresql > (the last only dll) built from source, and prebuilt msys from sourceforge > project. Please note that, if you provide binaries which are covered by the GPL, you must provide the corresponding source code for download *from the same place*. It isn't sufficient to point to the source on a different site. Alternatively, you can provide a written offer to supply the source code upon request, but that means that you have to keep those exact versions of the source code handy for the next 3 years (the website where you obtained it may cease to provide it when a new version is released). > Moreover, the installer procedure forces the user to install GRASS in a path > without spaces, to let it wotk properly, What's the problem with spaces? If any part of GRASS can't handle spaces in filenames, that's a bug which should be fixed. Also, some users may not be able to satisfy that requirement. The normal location for installing software often has spaces in the pathname (e.g. "C:\Program Files" on English language versions of Windows), as does the user's data directory (e.g. "C:\Documents and Setttings\"). All users can create files in their data directory, while the "Program Files" directory is normally writable by members of the "Power Users" group. OTOH, creating a new directory outside of those two locations may not be possible if the user isn't in the Administrators group. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
R: R: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer
Hi Michael, Hehehe... I would reply "just try" ;-) ... but it's not politically correct ;-) In the pure MS style, installer includes all: tcl/tk, sqlite, postgresql (the last only dll) built from source, and prebuilt msys from sourceforge project. Moreover, the installer procedure forces the user to install GRASS in a path without spaces, to let it wotk properly, and then dynamically creates: - grass63.bat, to correctly configure GRASS, basing on user selected install path - grass63, to let user launch GRASS from shell (configuring GISBASE and PATH variables accordingly to selected install path) - .grassrc6, to avoid the common first GRASS launch error - desktop shortcut to grass63.bat (to directly launch GRASS 6.3.0RC5) - StartMenu shortcuts to grass63.bat (to directly launch GRASS 6.3.0RC5) and msys.bat (to open an MSYS console) As an option, users can also download and install Spearfish GRASS sample DataBase during installation. Am I cool or not?? ;-DDD (I'm joking) Sorry, but now I need to go to bed. I must wake up until less than 6 hours; when it's late I have difficulties to write in italian... just imagine if I must write in english!! Goodnight Marco -Messaggio originale- Da: Michael Barton [mailto:[EMAIL PROTECTED] Per conto di Michael Barton Inviato: mercoledì 12 marzo 2008 1.06 A: Marco Pasetti Cc: grass-dev@lists.osgeo.org Oggetto: Re: R: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer Marco, Thanks very much. Does the wingrass...setup.exe file include tcltk and msys? Or do these need to be installed separately? Also, if msys is already installed, does it need to be installed again from your version? Thanks 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: On Mar 11, 2008, at 8:03 PM, Marco Pasetti wrote: > Hi Michael, > > Markus has uploaded all my recent jobs (excluding the building > guide) at > http://grass.osgeo.org/grass63/binary/mswindows/ > > Goodnight, > > Marco > > -Messaggio originale- > Da: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Per conto di Michael Barton > Inviato: mercoledì 12 marzo 2008 0.43 > A: grass-dev@lists.osgeo.org > Oggetto: Re: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer > > > > On Mar 11, 2008, at 11:52 AM, [EMAIL PROTECTED] wrote: > >> Date: Tue, 11 Mar 2008 13:20:59 +0100 >> From: <[EMAIL PROTECTED]> >> Subject: [GRASS-dev] WinGRASS-6.3.0RC5 Self Installer >> To: >> Message-ID: <[EMAIL PROTECTED]> >> Content-Type: text/plain; charset="iso-8859-1" >> >> WinGRASS Self Installer has been temporarily deleted from >> www.laser4000.it/temp/ I'm fixing some minor bugs; it will be >> available again whithin few hours at another internet location >> >> please be patient ;-) I'm working for you >> >> Marco >> -- next part -- An HTML attachment was >> scrubbed... >> URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/ >> 20080311/9512ee49/attachment-0001.html >> >> -- > > > Marco, > > I just want to say thank you again on behalf of all the windows users > among my students. As soon as the download location gets worked out, > I'll make a general announcement to the class. They'll be thrilled. > > Michael > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
