Re: Use of REQUIRED in Package Creation

VS> Ok. I should have elaborated a bit, REQUIRES is used eg. to "pull in" VS> the auto-autoloads of required packages at build time. Yes, I was using REQUIRES. That's what triggers the problem! VS> I think REQUIRES can eventually be used, and bet there's a bug lurking VS> somewhere currently. Possibly one of the below, or a missing autoload VS> cookie in hyperbole. VS> Here's a couple of things to check (dirs relative to packages top dir): VS> - Is oo-browser listed in package-compile.el (package-directory-map)? VS> *** I see that hyperbole isn't; it should be. Does adding them help? VS> - Is oo-browser in xemacs-packages/Makefile (PACKAGES)? Ding, ding ding! You get the prize. I had added oo-browser to package-compile.el and had posted to the group that hyperbole was missing. Of course, I didn't add hyperbole to my own copy! Now that package-compile.el has been updated with hyperbole, my package builds fine. VS> Posting an URL to a tarball containing your xemacs-packages/oo-browser VS> dir would be helpful... If I continue to have support issues like this, I will make it available for browsing. Good idea. Who do I speak to about getting cvs commit access so that I can put the oo-browser module under cvs control? And do I do this only after it's all working or can I do this even if it is still a work in progress? -- Jake Colman Principia Partners LLC Phone: (201) 209-2467 Harborside Financial Center Fax: (201) 946-0320 902 Plaza Two E-mail: colman(a)ppllc.com Jersey City, NJ 07311 www.principiapartners.com