Re: Head or Dev_1_3_bigcleanup

Michael Zimmermann wrote:

>> see docs/INSTALL section 3 (needed Perl Modules)
>
>
> As written in another mail last night I found the section about the perl
> module.
> As version 1.2 shipped with it's own set of modules I forgot to check.
> May be a sidenote in the upgrade document would be usefull. Something 
> like:
>
> "From version 1.3 ispman does not ship with it's own set of perl
> modules. Please make sure all the modules listed in "xxx" are installed.

Well, actually ispman 1.3 *does* ship with bundled perl modules 
(/contrib/perl) but they are not installed on default, leaving the 
decision to the user *which* modules to use (own, system, bundled).
I agree, that this should be mentioned in doc/UPGRADING.

>
>> Don't use dev_1_3_bigcleanup !!! It's probably dead-ended anyway,
>> since I already started a new backend from scratch with recyled
>> ispman code that eventually will be clean, > fast, neat and
>> webserviceable ;)
>
>
> Any targeted release date for this?

No, since I just started with it, and it's not even near alpha yet.
It will "only" provide a modular backend that preferably will be used by 
SOAP calls.
Others may then build nice & sexy GUIs (perl, php, python, whatever...) 
which use that backend webservice.
With current time constraints this will be nothing short-term, 
unfortunately.
As soon this will have some basic functionality, I will push this to CVS 
to open up for contribution and feedback.

Joerg



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl