Re: List of packages which should probably be Architecture: all
On Wed, Jan 02, 2008 at 09:39:17PM +0100, Aurelien Jarno wrote:
> Raphael Geissert a écrit :
> > Cyril Brulebois wrote:
> >
> >> On 02/01/2008, Pierre Habouzit wrote:
> >>> Though after a second thought, -dbg should probably not have empty
> >>> Depends line.
> >> After a third thought, I still fail to see what that has to do with
> >> being Architecture: all or any.
> >>
> >
> > Quoting my self (first message):
> >> This is usually bug either because of a missing Depends or because the
> >> package should be Architecture: all.
>
> I fail to see why. Imagine for example a -dev package providing only .h
> files, but depending on the architecture. It has to be Architecture: any
> and does not need to Depends on a package.
Most -dev package do not fall in this category because they
have a symlink to the shared library and thus have a Depends. This is
probably why it says "ussually".
Reasons why a -dev package can be arch any:
- It contains a static library.
- It contains headers that change depending on the arch.
Reasons why a -dev can have Depends:
- symlink to shared library
- The headers file in it use header files from an other library.
- The libtool .la or pkg-config .pc files mention other such files.
Kurt
Reply to: