Re: Bug#545464: Zombie cross packages

[Hector Oron <hector.oron@gmail.com>]

Hi,

En/na Neil Williams ha escrit:
> moving symlink /usr/lib/arm-linux-gnueabi/liblouis.so.2.
> moving file /usr/lib/arm-linux-gnueabi/liblouis.so.2.1.0.

> drwxr-xr-x root/root         0 2010-02-10 13:50 ./usr/arm-linux-gnueabi/lib/
> -rw-r--r-- root/root     42836 2009-07-07 00:11 ./usr/arm-linux-gnueabi/lib/libqofsql.so.1.0.1
> -rw-r--r-- root/root    245296 2009-07-07 00:11 ./usr/arm-linux-gnueabi/lib/libqof.so.2.0.1

For the cross toolchain, at the moment I have thought to use something like:

/usr/arm-linux-gnueabi$ tree -L 1
├── bin
├── include
├── lib
└── usr

/usr/arm-linux-gnueabi$ tree -L 1 usr/
usr/
├── include -> ../include/
└── lib -> ../lib/

That means cross toolchains will read
SYSROOT=/usr/arm-linux-gnueabi
INCLUDEDIR=/usr/arm-linux-gnueabi/usr/include -> (symlink)
LIBDIR=/usr/arm-linux-gnueabi/usr/lib -> (symlink)

 + I believe users will be able to point to any path, but just one
directory.
 + It keeps compatibility with what we have had until now.
 + Can handle multiple-sysroots
 + Easy to symlink multiarch dirs

It would be helpful to keep dpkg-cross as is, then start doing multiarch
aware stuff only if you pass some option in the command line. (-m
multiarch aware)

Does this sounds reasonable to you? At least as a starting point for
squeeze release. Then we can start trying out different ideas.

Kind regards,
  -- Hector Oron