Just a heads-up: I'm merging efs-cpan with efs-deploy, since the latter needs to use code from the former during the build process, and keeping them separate was turning into more trouble than it's worth.
The next master update for efs-deploy will include the cpan2efs code, and all it's modules. It will also be the end of the efs-cpan repo. I have also started working on "gnu2efs", which will do for the stuff in the gnu metaproj what cpan2efs does for perl5. This will include auto-discovery of dependencies by analysing the output of "configure --help". Imagine running: cpan2efs --updateall gnu2efs --updateall and after a few hours of automated builds, you have you entire perl5 and gnu metaproj's uptodate. This is a level of automation we only talked about in EFS 2. Well, for that matter, efsdeploy was a level of automation we only talked about, and both of these tools are another level higher. So, IFF anyone has an existing minicpan setup, beware that you are going to need to rebuild it and reconfigure cpan2efs before you can use the new code. OK, I have to get out of here. The echo hurts my ears..... _______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
