Re: Windows Installer for CLISP

[Sam S. <sd...@gn...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Elliott Slaughter wrote:
> On 11/5/07, Jack Unrue <jd...@gm...> wrote:
>> It would be cool if your script file(s) could be added to
>> the CVS repo. I guess it could go into the existing win32msvc
>> directory even though it's not specific to Visual C++.
> 
> Yeah, that is probably the next step. I don't know much about CVS... I
> downloaded some Tortoise CVS because it seemed easy to use, but I
> don't really know how to upload files to the server.

you won't be able to - you need write access for that, and before I can
grant you write access, you will have to get a sourceforge account.
you will have write access to the directory where the install files will
reside (win32msvc sounds fine).
actually, I would like to review the files before they go into the CVS.
Could you please make them available for download?

> One thing about the way I have been implementing the scripts so far:
> all my installer script files are named "install_..." because I placed
> them directly in the same folder as the clisp files, so I would know
> which files to ignore when grabbing files to install. I don't know
> what the setup will be like once I upload it to the server... I guess
> since individual developers (probably me) will be building the
> installer, I can depend on them to move the files to right place
> before running them... although perhaps I should change my assumptions
> about how the build process will occur. (Either way, this probably
> needs to be documented... see below.)

you can copy them over from win32msvc to the build directory.

>> I'd be willing to contribute a readme, if that helps.
> 
> That might be helpful, as noted above.
> 
> Also, since I am new to development, I am wondering on what level I
> get credit for working on this installer. I figure I can add my name
> to the source code of the installer script... but do I get copyright
> over the source of the script? I'm not sure what open source dictates

Your code remains copyrighted by you.
You are releasing it under the GNU GPL v2 or later, at the user discretion.
This means that the CLISP project can distribute your code with CLISP.
IANAL.

> Do I get to add a line with my to the copyright
> notice/license in the installer? Elsewhere?

I edit COPYRIGHT just to update the dates :-)
Bruno, as the main author, gets to decide who is mentioned there and how.
You do get a record in your name in the src/ChangeLog file (along with
dozens other CLISP contributors).

Thanks.
Sam.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHMIhBPp1Qsf2qnMcRAkbCAJ9iMQW2MhPHgmQGLd7XWRANpGr+bgCgl1B1
0a4SxfubFCDgRxjPT1ShwAs=
=abDh
-----END PGP SIGNATURE-----