On Wed, Jan 14, 2004 at 07:26:53PM +0100, Goswin von Brederlow wrote:
> Hi,
>
> You all have seen the other thread about multiarch? This one is a
> different part of the puzzle.
>
> The proposal is to make all *-dev packages "Architecture: all". This
> should be a strong should or must directive and a must for
> built-essential for sarge+1.
Among all the other reasons this is a bad idea there is one that makes
it very annoying.
libfoo1
Arch: any
libfoo1-dev
Arch: all
Depends: libfoo1 (${Source-Version})
A new version of libfoo1 is uploaded the archive, m68k (eg) hasn't built
it yet but needs to build something that depends on it.
m68k
----
libfoo1 1.0-1
libfoo1-dev 1.0-2
Depends: libfoo1 1.0-2
Therefore, libfoo1-dev isn't installable until it has been built on that
arch. Right now this problem exists in the archive for the dev packages
that essentially violate policy by being Arch: all. With all the dev
packages being Arch: all it will be much more of an issue.
Practical example is libqt3-mt-dev since it depends on a separate split
out headers package which is Arch: all. Since it took over a week for it
to build on m68k all the packages uploaded since then that depend on it
have failed and have to be manually set to Dep-Wait.
So unless you come up with a way to have the old -dev packages exist on
the arches that still need them its a very bad idea for them to be
Arch: all.
BTW - kde-config is used at runtime and is a c++ program not a script.
Chris
Attachment:
signature.asc
Description: Digital signature