Bug#514016: Bug#514015: options for fixing

[Bastian Blank <waldi@debian.org>]

On Thu, Feb 05, 2009 at 06:20:24PM +0100, Thomas Viehmann wrote:
> just as an exercise what might be done to fix this:
> It would seem that the options are
> - find something in current tar that works (I didn't),

There is nothing.

> - switch off tar,

I intend to replace tar with a custom unpack routine in cdebootstrap.

> - try to do something with tar
>   (new upstream - vs. release: ugh - has a "apply to symlink target"
>    --transform flag, but that also might need post-processing of
>    symlinks at end of bootstrapping),

What would dpkg do with the symlinks in the the unpack phase?

> - try to do some ld-preload(?) trickery for changing the way symlinks
>   are read,

fakechroot have to do this someway, but I was unable to grok that code
yet.

> - try to find some way to chroot before calling tar, one possibility
>   would be copying required files to some temp CWD, make tar look there
>   for the libraries, chrooting to the target and calling tar from (the
>   unchanged) CWD,

Rather hacky. Would mean to include mklibs-copy or similar
functionality.

> - add chroot option to tar (see patch).

This is a root only option.

Bastian

-- 
Conquest is easy. Control is not.
		-- Kirk, "Mirror, Mirror", stardate unknown