Re: Windows Installer for CLISP

[Elliott S. <ell...@gm...>]

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.

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.)

> 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
with respect to this. Do I have any intellectual rights to my code? Or
is this simply my contribution to the community, and this project (and
thus its legal rights) now falls into the hands of everyone in the
clisp project? Do I get to add a line with my to the copyright
notice/license in the installer? Elsewhere?

Thanks for answering my questions.

-- 
Elliott Slaughter

"Any road followed precisely to its end leads precisely nowhere." -
Frank Herbert