Re: libg++-2.7.2.deb is old?

[bruce@pixar.com (Bruce Perens)]

Me:
> It's complaining that it can't find the interpreter for the
> pre-installation script in the perl package.

From: Amos Shapira <amos@dsi.co.il>
> Which interpreter?  When I run "dpkg -I" on the perl package I see only
> #!/bin/sh scripts.  And if it's missing (whatever it is) then what should
> I do to install it?

It's expecting to be able to run the shell on that partition in a "chroot"
context - this requires all of the shared libraries needed to start the
shell, etc. Try something like this (assuming the test partition is on
scratch):

	cd /scratch
	chroot /scratch bin/sh

If that doesn't work, you should be able to figure out why. This may
indicate a bug in dpkg's --root flag if that _does_ work. I have a
vague memory of something like this happening before. The _current
directory_ before you run it may be important - try to cd to /scratch
before running it.

> Isn't it possible to supply a "usable" base tree?  Why can't a fully
> configured tree be provided?

The only stuff that isn't configured is stuff like the host name, the
resolver configuration, the network configuration, and the mount table:
all things that require some user input.

> I might be totally wrong here, but I'd like to test things by manually
> installing whatever is need to be done, rather than let dselect and
> the boot disks do their magic behind my back.  I think I'd just feel
> more comfortable with the resulting image if I knew what actually is
> happening in there.

That is indeed prudent. I think you have to learn all of the "magic" that
they do so that you can duplicate it manually. Install the boot-floppies
package and read the scripts under /usr/src/boot-floppies . If you don't
have time for this, create a CD-writable pre-master, and go through the
entire installation process with it (magic and all). Then you can come back
and learn the magic later on.

>> The libg++ doesn't compile with the ELF libc. That's why it's in that
>> state. I'm not sure what's happening with this - whether there is a
>> maintainer working on it or if we're just going to wait for GNU LIBC 6.

> I understand.  But what's the difference between the "--root=..."
> environment and without that would cause such a message?

Presence of the a.out libraries in /scratch?

I think once you walk through the way I build base1_1.tgz in the
boot-floppies package this will make more sense.

	Thanks

	Bruce