Re: [Eis-devel] question

[Bas L. <ba...@ba...>]

Hi Luuk,

First of all apologies for my terribly late reaction.

I think that installation of modules should be done by simple creating 
zip archives of a module
directory. The install tool in the servermanager should then in my 
opinion first extract this zip file to
a temporary location. This temporary directory can then be checked to 
verify that the zip is indeed
a valid EIS module (contains a module.xml, elements dir, locales, 
services etc.) and basic info from the
module.xml can be displayed. If everything is ok you can then choose to 
install the module to the modules
directory.

Cya

Bas

Luuk van den Broek wrote:
> He guys,
>
> Iv'e done some work on the servermanager. Almost all elements are done. 
> Only thing left are the dependencies between environments and 
> applications and such.
>
> Another thing that is left is the element that used for adding modules. 
> I was wondering what methods we were going to use to add modules. Just 
> normal folders or zips and if the modules would be prepackaged and done 
> or stuff like module.xml should be rendered if not present , Possible 
> checks? etc...
>
> I was thinking that at least support for compressed modules should be 
> added (zip tar etc.) The rest i'm not sure about.
>
> Let me know
>
> Luuk
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Eis-devel mailing list
> Eis...@li...
> https://lists.sourceforge.net/lists/listinfo/eis-devel
>