On Thu, Jan 26, 2012 at 3:50 PM, Phillip Moore <[email protected]>wrote:
> > That is quite cool. About the only thing I could think of that would > make > > it even simpler would be to overload 'use' inside Perl core. This > syntax, > > though, is _really simple_. > > That would be cool, but the problem is that 'use' would have to be > able to map a module name to a distro to a project, etc. OTOH, you > would only do this if you were about to die *anyway*, so it might be > feasible. > > IIRC, Jerry and I looked into doing something like this, back when we > were exploring options, and right before I stumbled across > sitecustomize.pl. It would require patching the core perl C code, > which I have tried to avoid (although we *DO* patch the perl core to > add error checking for sitecustomize.pl). > > Yeah, it's hairy. I pulled up the source myself before sending this email, just to see how bad it would be. I think the answer is 'pretty bad'. > > >> EFSPERL_DEPENDS > >> EFSPERL_DEPENDS_GLOBAL > >> EFSPERL_NO_OBJECTS > >> EFSPERL_DEBUG > >> EFSPERL_DUMPINC > >> > >> I'll listen to suggestions for others.... > > > > When I first looked this, I had a slight preference for the EFS_PERL_* > > syntax because of ease of using split(), but after I thought about it a > bit, > > the ability to parse out 'EFS' and 'PERL' is fairly trivial either way. > So > > either naming convention works fine for me.. > > I must have switched between EFS_PERL_* and EFSPERL_* 10 times while > writing that email, which shows I'm on the fence, too. > > Next time I have a reason to hack on efs-perl, I'll add these. BTW, > if you *are* going to install this latest release RSN, let me know, > and I'll get the env var patch in before you do. > All joking aside, I expect to be working on EFS 3 within the next week (ie, starting the bootstrap process), and expect to have something others can look at certainly within two months. Various other components for having something others can play with are out of my hands, but, best-case is that I get them within two weeks; worst case is, well, that's why I said within two months.. I'll keep you posted as that time draws near. That actually brings up an important item: what exactly is EFS 3? There is no release tag in efs-core, much less something that crosses the various git repos to tag everything as being related with the EFS 3.X release. Is anyone planning on making a set of tags? Steven
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
