Skip to contentSkip to conversation

org.oe.dev disapproval of revision '66573a06c1ee62e38d70a6c82f8d99a41243cd5c'

oe-commits Dr. Michael Lauer 3 participants 5 messages Jul 7, 2007 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 1 line · koen commit

disapproval of revision '66573a06c1ee62e38d70a6c82f8d99a41243cd5c'

May I request that from now on _every_ disapproval goes hand in hand with a lengthy explanation on oe-devel?

Regards,

:M:

Signature · 1 line
Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de
#2 lore raw

While koen is on the train I think it would be appropriate to quote his doppelgänger in Edinburgh:

<koen|edinburgh> ~botmail for woglinde: *NEVER* DEPEND on libiconv directly, but on virtual/libiconv, otherwise you break all glibc based builds out there

Love,
H

Quoted 9 lines · Dr. Michael Lauer
Quoted 1 line · koen commit

disapproval of revision '66573a06c1ee62e38d70a6c82f8d99a41243cd5c'

May I request that from now on _every_ disapproval goes hand in hand with a lengthy explanation on oe-devel?

Regards,

:M:

#3 lore raw
In reply to Dr. Michael Lauer

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dr. Michael Lauer schreef:

Quoted 5 lines
Quoted 1 line · koen commit

disapproval of revision '66573a06c1ee62e38d70a6c82f8d99a41243cd5c'

May I request that from now on _every_ disapproval goes hand in hand with a lengthy explanation on oe-devel?

Yes, sorry about that, I wanted to act quickly before people with glibc builds get the change, build libiconv and require a build from scratch.

The bottom line:

*NEVER* DEPEND on libiconv directly, but on virtual/libiconv, otherwise you break all glibc based builds out there

The situation is tricky since uclibc (and maybe newlib) need libiconv, but our glibc build can use the internal iconv from libc6.so. That's why we have virtual/libiconv which does the right thing automagically.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGj6hgMkyGM64RGpERAhQSAJ9BRu5yEB5IB3aS6s2p/u5IsErOSQCeOL3e QazmT2c2fB9En+b0UZkhF4o=
=qFg1
-----END PGP SIGNATURE-----

#4 lore raw
In reply to Dr. Michael Lauer

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dr. Michael Lauer schreef:

Quoted 5 lines
Quoted 1 line · koen commit

disapproval of revision '66573a06c1ee62e38d70a6c82f8d99a41243cd5c'

May I request that from now on _every_ disapproval goes hand in hand with a lengthy explanation on oe-devel?

Yes, sorry about that, I wanted to act quickly before people with glibc builds get the change, build libiconv and require a build from scratch.

The bottom line:

*NEVER* DEPEND on libiconv directly, but on virtual/libiconv, otherwise you break all glibc based builds out there

The situation is tricky since uclibc (and maybe newlib) need libiconv, but our glibc build can use the internal iconv from libc6.so. That's why we have virtual/libiconv which does the right thing automagically.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGj6hgMkyGM64RGpERAhQSAJ9BRu5yEB5IB3aS6s2p/u5IsErOSQCeOL3e QazmT2c2fB9En+b0UZkhF4o=
=qFg1
-----END PGP SIGNATURE-----

#5 lore raw
Quoted 13 lines · Koen Kooi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dr. Michael Lauer schreef:

Quoted 5 lines
Quoted 1 line · koen commit

disapproval of revision '66573a06c1ee62e38d70a6c82f8d99a41243cd5c'

May I request that from now on _every_ disapproval goes hand in hand with a lengthy explanation on oe-devel?

Yes, sorry about that, I wanted to act quickly before people with glibc builds get the change, build libiconv and require a build from scratch.

Quoted 8 lines

The bottom line:

*NEVER* DEPEND on libiconv directly, but on virtual/libiconv, otherwise you break all glibc based builds out there

The situation is tricky since uclibc (and maybe newlib) need libiconv, but our glibc build can use the internal iconv from libc6.so. That's why we have virtual/libiconv which does the right thing automagically.

Excellent. Thanks for the explanation.

Cheers,

:M: