Re: Changed ISPMan Installation
Wim Kerkhoff <[email protected]>
| Newsgroups | gmane.comp.isp.ispman.devel |
|---|---|
| Message-ID | <[email protected]> |
Atif Ghaffar wrote: > Hi Joerg, > > Sorry about the late feedback but been so busy lately.... > > Joerg Delker wrote: > >> * The bundled perl modules were removed from the lib directory. >> Necessary perl modules are still bundled though, but are not part of >> the standard install process. Either bundled or CPAN modules can be >> installed separately (see docs/INSTALL). > > > I dont like this idea but.. if others like it, I am ok with it. Also I > like that you are still providing the bundled modules separately. > > I have installed some programs like amavisd-new etc that require tons > of modules and the installation takes so much time that at some times > I gave up. Eventually I made my amavisd package that contained all the > modules that were required and the ones I tested and worked in > production environment. > > The installation after was just a matter of extracting my tar file and > type make in it. This would compile and install all the modules and > installation would finish in minutes. > > The same idea was with ISPMan. That it works with minimum installation > overhead. This is the same reason that I carefully selected some > modules over others. I used the modules that required no compiling > etc. (The exception is the Text::Iconv module which was very recently > introduced). > The problem is that once there is a new module in CPAN, immediately your tar file is out of date. Any decent/recent Unix/Linux operating system has decent package management that handles all these dependencies, downloading, and installing them. For example, Debian already has packages of many CPAN modules. With the CPAN.pm module, it's super easy to script out actions such as checking that a list of modules are installed, and if not prompting the user whether to automatically install them. So my opinion (for what it's worth :-) ) is that removing those modules from the lib/ directory is a good step. Having them bundled as tarballs in CVS feels kludgy; the "CVS way" is to store only scripts/code in CVS, not binaries (compressed/compiled code). So, a simple script that uses wget to download all the modules directly from a CPAN mirror makes more sense. I run amavisd-new on several servers... all I do is run 'apt-get install amavisd-new clamav' and it handles everything :-) > > > > I wont be able to give much feedback before I start working on ISPMan > again. This basically means that I have a client that requests > installation/customization/integration services. > > So send me customers ... hint .. hint.. We're adding more and more domains, so hopefully soon (after some other stuff is out of the way) I can contribute some more like I've been promising. Regards, Wim ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285