Marco: > >> 2) branches/develbranch_6/win32 > >> > >> the folder where i put all the scripts and files > >> needed to prepare the release installer (as an exe file). > > >why refer to 32bit in the dirname? > > Good question; actually I named it as I'm used in my > windows projects, because I build on a 32 system; > BTW, I don't know if MSYS/MinGW + NSIS are available > even for Win64... > For me it's the same... We can call it just > "Windows"
too generic- we use X-windows and rastr regions are call "windows" internally. why not just use the same as on the website: mswindows? > >> Just few questions: all the files (dos batch scripts, the > >> NSIS script, icons and documents) are made by me, with the > >> exception of: > >> > >> 2.1) the bmp files (4) for the installer GUI, > >> taken from the standard > >> library of NSIS (that is OS, obviously) > > > it may be "open source", but that means 1001 different things, many > > of which we can not touch. what is the license exactly? are > > those 4 files distributed under terms compatible with the GPL? > > If not GPL is it one of the OSI usual-suspects approved set? > > From the NSIS official web site: > > Applicable licenses > -------------------------------------- > > * All NSIS source code, plug-ins, documentation, examples, > header files and > graphics, with the exception of the compression modules and > where otherwise > noted, are licensed under the zlib/libpng license. > * The zlib compression module for NSIS is licensed under > the zlib/libpng > license. > * The bzip2 compression module for NSIS is licensed under > the bzip2 license. > * The lzma compression module for NSIS is licensed under > the Common Public > License version 1.0. > > zlib/libpng license > -------------------------------------- > > This software is provided 'as-is', without any > express or implied warranty. > In no event will the authors be held liable for any damages > arising from the > use of this software. > > Permission is granted to anyone to use this software for > any purpose, > including commercial applications, and to alter it and > redistribute it > freely, subject to the following restrictions: > > 1. The origin of this software must not be misrepresented; > you must not > claim that you wrote the original software. If you use this > software in a > product, an acknowledgment in the product documentation > would be appreciated > but is not required. > 2. Altered source versions must be plainly marked as such, > and must not be > misrepresented as being the original software. > 3. This notice may not be removed or altered from any > source distribution. > > About the above mentioned terms: > > 1. done: > http://grass.osgeo.org/grass63/binary/mswindows/native/#Install%20GRASS > 2. I didn't altered the source, I'm using only the > binaries > 3. We are not distributing the source code > > >> 2.2) a small part of the installer, a function to let replace > >> parts of strings; I just copied and pasted it, maintaining > >> the header, where is clear the line ";Written by [author]" > > > what license terms did the author provide it with? you can not > > just cut and paste things from the internet or "cook books", > > even with attribution. is it a simple one-liner that is hard > > to write any other way, or is it an original work? > > without a clear license you can not distribute the code. > > I found it on the wiki/examples section of NSIS site > http://nsis.sourceforge.net/StrRep > Since it's an example it lays in the zlib/libpng > license mentioned above. > In particular, as I didn't modified the code, it > respects all the terms in it. as "examples from website" is clearly put in the license statement, it seems like no extra effort is required there. Hamish _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
