Re: [multiarch] Proposal for *-dev packages

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Daniel Kobras <kobras@debian.org> writes:

> On Wed, Jan 14, 2004 at 07:26:53PM +0100, Goswin von Brederlow wrote:
> > 2. different header files per architecture
> > 
> > The differences in the headers can be merged by using preprocessor
> > conditionals.
> 
> How to include arch-specific information that is probed at configure

That would be either static information that can be gathered once and
hardcoded into the headers or its information particular to the buildd,
which should never make it into the -dev package.

> time? What about porting to new archs when there's no preprocessor
> conditional yet?

Add one to gcc first thing in the morning. Or set -D__NEW__ in the
compile flags.

> > 3. support binaries in the -dev package
> > 
> > I'm thinking about gtk-config, sdl-config, kde-config, ...
> > Are all of those scripts or are there some compiled programs in hte
> > mix?
> 
> Same problem here. Those scripts may contain arch-specific data, eg.
> arch-dependent CFLAGS.

There are just so many archs that can easily all be included and
the right one chosen at runtime.

> > I suggest splitting any binary programms (if there are any) out into a
> > -helper package and have the -dev depend on them.
> 
> Now instead of -dev, the -helper packages conflict. So what was the
> purpose again?

The -helper package should either work for both archs or both should
be installable at the same time (/usr/lib/package/helper and
/usr/lib64/package/helper works fine). I don't expect this to be more
than a handfull cases if at all.

MfG
        Goswin