Chris McDonough writes: > Actually, both of these directories have historically worked in much > the same way as the Products package does.
Ok, well, that's still not hard to do; we just add the bootstrap directories to each of the lists once we've read the config. > A software home may have (actually currently must have) an "import" > directory. Zope currently slurps various TTW "examples" from a zexp > file in the software home import directory. I'd really like to dump > this dependency, but it would take a bit of work. Ah, that's right. I keep trying to forget about that. One approach may be to use the import mechanism but not the import search mechanism for that. So there's still a .zexp file in the software, but it's not part of the general import/export support. > The Extensions directory... errr.. this should probably not be in a > software home anymore. I can't think of anything that would break were > it to not be there anymore (besides products that depend on the physical > layout of the software home, which shouldn't exist). So this one doesn't present a problem. The default list will only include the Extensions in the INSTANCE_HOME, and configuration will override that if something else is desired. > Personally, I think we should just hardcode '/home/fred/zope/import' > into the core as the import directory and be done with it. ;-) That's fine with me. At least it won't be accessing *your* imports directory. ;-) -Fred -- Fred L. Drake, Jr. <fred at zope.com> PythonLabs at Zope Corporation _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
