Re: What to do with modules now ...

Bill> I think andy's concern was with the fact that they will need to be Bill> _installed_, and then you might not be able to share install trees or Bill> something like that. Currently the only file that has to `agree' specifically with the binary is the DOC file. So we'd have to finally properly solve the problem of finding a unique place to put the DOC file, since the modules will have to go there as well. What makes this tricky is that these files are not merely architecture-dependent, but also configure-flag-dependent. I don't see an easy answer. In some ancient email I suggested a --flavor or --moniker configuration flag, that would identify THIS xemacs binary. Then the DOC files and modules could be stored under $VERSION/$ARCH/$FLAVOR or something. Martin