Douglas Kline <[EMAIL PROTECTED]> said:
>
> Now I'm getting a different error: The variable basepath is being defined to
> its own name as a value in Engine.pm. When Engine.pm starts, the variable is
> undefined. In the initialize sub-routine in Engine.pm it's defined in the
> command
>
> $self->{basepath} = $basepath = $config->param("basepath")
>
> to its own name which, of course, leads to an error.
>
> Earlier tests before I ran into this problem showed that fink was able to
> locate the pathnames correctly in at least some cases. Any ideas as to what's
> going wrong here? Should that sub-routine in Engine.pm be getting the correct
> value from somewhere or should it be set elsewhere?
I don't understand that analysis. The $config object, which is a
Config not an Engine, was established in Engine::new_with_config().
What's the exact error you're getting? Insert some print statements
there to see what the values are.
>> If dselect is the stumbling block, just hack the apt package to avoid
>> building it.
>
> So far as I can tell, dselect isn't the stumbling block since it's not
> mentioned in the error messages and the routines to which I've traced errors
> aren't building dselect. I mentioned it because the documentation says that
> it's one of the tools that this installation creates and it wasn't created.
I've heard that the bootstrap script sometimes doesn't abort if there
are certain package-building errors. That means one gets incomplete
packages, and perhaps some chunks of the build process aren't being
run. It would be in the "dpkg" package if it were created.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
_______________________________________________
Fink-beginners mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-beginners
