This is embarassing....    The bootstrap fails for the same reasons (I am
99% sure) that it failed for Colin last week: the efs-core code depends on
the latest Moose (by accident), and the /usr/efs tarball has to be updated
otherwise the code won't work.

This is the endless CPAN dependency nightmare, which never ends.

The main challenge is trying to keep the set of module versions we use in
/efs/dist (via EPD, cpan2efs, and all of that infrastructure) in sync with
what gets installed into /usr/efs when we build the tarball.  That's HARD to
accomplish, since we're using totally different mechanisms to create the two
sets of depenencies.

I have been trying to rationalize this, with minimal luck.   I started
developing a totally new bootstrap mechanism (export to /efs/boot) that
would solve this problem, but that's still a WIP (it's HUGE , for one
thing).   Until that works, the only way to build /usr/efs is using
efs_bootstrap_install (to build it, not download it), and that uses cpanp
against the "head" of CPAN.

I can change efs_bootstrap_install to use /home/minicpan/latest, but there
will still be differences, and in the past, even subtle differences can
result in functional problems.  Most of what we're working with in
/efs/dist/perl5 (in Jerry's setup -- the only working EFS 3 environment
right now) was build from /home/minicpan/latest, but even that will be newer
than what we've installed when I build against it.

Short term, I have no choice: have to use the existing mechanism.

Long term, I want to get the /efs/boot approach working, so that what we
bootstrap with, is IDENTICAL to what we're testing and developing with.

This is extremely frustrating, because the bootstrap process is the first
thing new EFS users "see" about this infrastructure, and noone understand
the complexity of the problem: they just think our software sucks because it
doesn't install easily.

Maybe it does.... (suck, that is...)
_______________________________________________
EFS-dev mailing list
[email protected]
http://mailman.openefs.org/mailman/listinfo/efs-dev

Reply via email to