Re: Use of REQUIRED in Package Creation
>>>> "VS" == Ville Skytt <Ville> writes:
VS> On Mon, 2003-07-21 at 21:09, Jake Colman wrote:
> Under what circumstances must REQUIRED be used? I have a package
that
> requires another package to be installed in order for it execute. I can
> build the package, however, without specifying that package in REQUIRED and
> if I do specify it the build fails. The build works because my PRELOAD looks
> for the other package in the load-path and sets things up accordingly.
> As long as the other package has been installed, I am ok.
VS> To me it looks like you're using it correctly, but just to verify, you
VS> are using REQUIRES in Makefile, not REQUIRED?
Yes, REQUIRES. Sorry, typo.
> So, do I have to bite the bullet and figure out why my build
fails or can I
> leave it out of REQUIRED? If REQUIRE is only for build-time issues than I am
> OK. If REQUIRE is used so that the package management facility knows each
> package's runtime prerequisites than I am stuck.
VS> It's kinda both. It's really for build time dependencies, but the
VS> package ui uses it to suggest (not enforce) installation of
"dependent"
VS> packages (see 'r' in the "List and install" view).
Hmmmm. My package definitely requires the other one or it cannot be used.
So, first I need REQUIRES to work so that the package GUI can make the proper
suggestion. I also need to enforce that the dependant package is actually
installed.
Oy! How do I do this? And how can I track down why I cannot compile if I
use REQUIRES?
--
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