Re: cross-gcc status
>> - - bad default for crossbase (it *should* be /usr, there is no point
>> to make it different unless toolchain is able to handle that) - this
>> may be fixed immidiatly
This is already commited
> FWIW, I've always wished dpkg supported relative paths; for instance
> $BIN/foo or $LIB/bar.1.so
> Since $CROSSINC would be resolved when packages were installed, instead
> of when they were built, one package could support different
> configurations of $CROSSINC, $CROSSBASE, etc.
What you write about seems to be a major change in debian packaging system.
Although it may be useful, I doubt such a change will be accepted by debian
in forseable future.
As for dpkg-cross, I'll try to keep it consistent with other packaging