Guillem Jover wrote:
Just to clarify, the version in etch is not going to be updated for
this anyway, that's Debian release policy.
Didn't expect it would.
I issued a bug because I thought it would be nice to have a record of
etch dpkg-architecture breaking when the toolchain advertises itself as
an uclibc toolchain.
Given other conversations, I take this is for Maemo. And my same
concerns apply, why do you need a new architecture? And do you realize
this would imply having two different dpkg db (there's no multiarch
support yet anyway)?
Yes, I know.
You're correct, the patch is for maemo. The bug however, is about
debian. However it will be handled in maemo, is, in the end, not
relevant here.
Meanwhile, made this horrid patch to get the architecture recognized as
armel, as with the ordinary arm+glibc equivalent.
This is the completely wrong approach, I'd recommend you don't do that
in Maemo either.
I realize that.
As I said earlier, the patch here is a quick (and ugly) fix to
circumvent a problem with dpkg-architecture searching specifically for
-gnueabi in architecture strings.
It's not intended as a solution. It was a way to create armel packages
which are built against uclibc instead of breaking down completely.
Regards,
Jussi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
