My two cents:

An installer worries me on many levels. I wouldn't release it with 
1.3.0. I would put it out there separately as something needing testing 
and feedback on non-production machines.

The only reason I say this is that the installer introduces complexity 
and abstraction from the process and will make helping people new to 
ASSP all that more difficult.

As far as creating an installer, I would suggest looking at Innosetup 
also.  Its free and has great scripting capabilities (see third party 
tools [istool])
http://www.jrsoftware.org/isinfo.php

Best,
Chris




Kevin wrote:
> Fritz Borgstedt wrote:
>   
>> TreeWalk <[EMAIL PROTECTED]> schreibt:
>>     
>>> Uhm .. wait a minute.. why carrying all the perl modules with ASSP
>>> when the modules may be updated (e.g. bugfixes etc..) ? I think it
>>> may be a good idea to setup a cmdline perl script sitting inside
>>> the ASSP folder; at that point to setup ASSP one would just need
>>> to install a working perl, extract the ASSP files into whatever
>>> suitable
>>> folder and run the "setup.pl" script; the script in turn will proceed
>>> to
>>> download and install all the needed bits and pieces (perl modules)
>>> create the required folders (if not already there) and so on; I think
>>> this
>>> may be a good idea; especially since the same script may then be
>>> used for multiplatform setups *and* since it may be called from any
>>> "automated installation tool" :)
>>>       
>> Yep, and the planning of the next vacation should also be included.
>> You are free to put 6 month in it. I will not.
>> I will go with my solution of a frozen environment - but no problem, i
>> will offer it only to MacOS X.
>>
>>     
>
> To be perfectly honest Fritz, I've already written a script that does 
> all he talked about, it only requirement is a basic install of 
> activeperl, it downloads, installs(with required modules), and starts 
> ASSP (though it's only for win32 since most platforms have their own 
> unique install method).
>
> I just think a true installer(*cough* without .NET 2.0 *cough*) would be 
> a better solution.
>
> I'm very curious to the "frozen environment" you are talking about and 
> look forward to seeing how you implement it.
>
> Kevin
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Assp-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-user
>
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to