On Tue, Jun 15, 2010 at 10:47 AM, Anthony Skipper <[email protected]> wrote: > I'm curious about what can be done to simplify packaging and installation of > EFS. I've encountered a number of problems that make it a bit difficult to > use OpenEFS in both corporate and commercial environments. > > The first is the basic install instructions. Threre don't seem to be any. > I've now worked through installing OpenEFS a couple times on ubunutu and > partially on Centos 5.3 and would be happy to send you my notes if that > would help as a starter? I have to say that hacking through MakeInstall.pl > and debugging dependencies is never fun. Even less so if you happen to be a > Perl neophyte like myself. Unfortunately I haven't had time to make expect > scripts for all the basic scripts I put together, but maybe it would be > helpful regardless. It seems like the optimal scenario would be to get to a > point where someone could just "yum/apt-get/rpm OpenEFS", and then just jump > to configuring the client and server conf files. It would be especially > nice to have both the CPAN modules and other dependencies in a single > package. >
It seems you've missed the efs-core/doc/efs_bootstrap* documents. (Caveat -- I haven't look at the changes in the past month, so I may be out of date). Note that efs_bootstrap_install sets up your Perl environment (i.e., perl 5.10 + modules you need and puts them in an efs-specific location so that they don't interfere with your existing Perl infrastructure. That answers the objection you raise below. I've also found the irc channel to be very helpful in the bootstrap process, as there were quite a few hurdles -- I know the team has worked hard on that, but I haven't gone back and tried a re-install recently. Steven > The other issue I encountered is the dependency on Perl5.10. Many of the > folks we work with are on some combination of RHEL/Centos 4.8-5.1. But all > those versions and even the later 5.3 & 5.4 series use a version of Perl > older than 5.10. If you know RHEL and Centos then you know that replacing > the version of perl that comes bundled with the platform can break so many > things. (The only way I know to make it work is to strip the OS down to the > ground and rebuild all the packages all the way back up, which isn't a valid > approach in the real word) It would be a lot easier if both the install > script and the code itself could be configured to use a separate perl > installation than the default of the platform. > _______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
